Potential Data Exfiltration Path

What Foo Guard detects

The agent combines explicit data-reading capabilities with arbitrary outbound network access and no human approval boundary. This indicates a potential data exfiltration risk, not confirmed exfiltration behavior.

When this rule triggers

humanApprovalRequired is false and the agent has both data-reading and arbitrary HTTP capabilities; these may be separate tools.

Foo Guard evaluates the normalized configuration supplied to the scanner. A finding describes configuration risk; it does not establish that an attack occurred. An absent finding does not prove that an undeclared capability is safe.

How to fix

Constrain outbound destinations, minimize accessible data, and require approval where sensitive data could leave the trusted boundary. This finding is a potential path, not proof of exfiltration.

Verify the change

Update the actual agent configuration and the underlying permissions or controls, then run the scanner again. Inspect the finding’s evidence path to confirm the intended setting changed. Do not clear a finding by changing a declaration that no longer reflects the deployed agent.