Conflicting Read-Only Tool Declaration

What Foo Guard detects

The same tool explicitly claims to be read-only while declaring writing, modification, or destructive behavior. Descriptions and names alone are not used. MCP hints do not establish enforced behavior.

When this rule triggers

The rule triggers when The same tool explicitly claims to be read-only while declaring writing, modification, or destructive behavior. Descriptions and names alone are not used. MCP hints do not establish enforced behavior.

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

Align declarations with actual behavior and enforce write restrictions in the tool or host. Do not auto-approve actions solely because a tool advertises a read-only hint.

Align declarations with actual behavior and enforce write restrictions in the tool or host. Do not auto-approve actions solely because a tool advertises a read-only hint.

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.