Low Risk

dump_codebase_context

Recursively reads text files from a specified directory, respecting .gitignore rules and skipping binary files. Concatenates content with file path headers/footers. Supports chunking the output for large codebases.

Part of the Codebase Context Dumper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call dump_codebase_context to retrieve information from Codebase Context Dumper 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 dump_codebase_context 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.

lex-tools-codebase-context-dumper.yaml
tools:
  dump_codebase_context:
    rules:
      - action: allow

See the full Codebase Context Dumper policy for all 1 tools.

Tool Name dump_codebase_context
Category Read
Risk Level Low

Agents calling read-class tools like dump_codebase_context 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 dump_codebase_context tool do? +

Recursively reads text files from a specified directory, respecting .gitignore rules and skipping binary files. Concatenates content with file path headers/footers. Supports chunking the output for large codebases.. It is categorised as a Read tool in the Codebase Context Dumper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dump_codebase_context? +

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

What risk level is dump_codebase_context? +

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

Can I rate-limit dump_codebase_context? +

Yes. Add a rate_limit block to the dump_codebase_context 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 dump_codebase_context completely? +

Set action: deny in the Intercept policy for dump_codebase_context. 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 dump_codebase_context? +

dump_codebase_context is provided by the Codebase Context Dumper MCP server (lex-tools/codebase-context-dumper). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Codebase Context Dumper

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.