Risky Actions with Logging Disabled

What Foo Guard detects

A tool explicitly declares writing, modification, or destructive behavior while agent logging is explicitly disabled. External audit controls are not assessed.

When this rule triggers

The rule triggers when A tool explicitly declares writing, modification, or destructive behavior while agent logging is explicitly disabled. External audit controls are not assessed.

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

Enable agent action logging with identity, target, outcome, and appropriate retention. Exclude secret values. Verify any external audit boundary before recording an exception.

Enable agent action logging with identity, target, outcome, and appropriate retention. Exclude secret values. Verify any external audit boundary before recording an exception.

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.

Test the affected workflow in an isolated environment, including an operation that should be denied. Keep related findings in view: fixing this rule does not automatically resolve other identity, permission, tool, or audit risks.