Low Risk

faf_debug

Debug Claude FAF MCP environment - show working directory, permissions, and FAF CLI status

Part of the Claude Faf MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call faf_debug to retrieve information from Claude Faf without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though faf_debug only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

faf-project-dna-for-ai-context-on-demand.yaml
tools:
  faf_debug:
    rules:
      - action: allow

See the full Claude Faf policy for all 33 tools.

Tool Name faf_debug
Category Read
Risk Level Low

View all 33 tools →

Agents calling read-class tools like faf_debug have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the faf_debug tool do? +

Debug Claude FAF MCP environment - show working directory, permissions, and FAF CLI status. It is categorised as a Read tool in the Claude Faf MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on faf_debug? +

Add a rule in your Intercept YAML policy under the tools section for faf_debug. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Claude Faf MCP server.

What risk level is faf_debug? +

faf_debug is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit faf_debug? +

Yes. Add a rate_limit block to the faf_debug rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block faf_debug completely? +

Set action: deny in the Intercept policy for faf_debug. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides faf_debug? +

faf_debug is provided by the Claude Faf MCP server (claude-faf-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Claude Faf

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.