High Risk →

doc

Generates Rust documentation and returns structured output with warning count.

Accepts file system path (path); High parameter count (14 properties)

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

@paretools/cargo Execute Risk 3/5

AI agents invoke doc to trigger processes or run actions in Cargo. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

doc can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-dave-london-cargo.yaml
tools:
  doc:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Cargo policy for all 12 tools.

Tool Name doc
Category Execute
MCP Server Cargo MCP Server
Risk Level High

View all 12 tools →

Agents calling execute-class tools like doc 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 Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

doc is one of the high-risk operations in Cargo. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the doc tool do? +

Generates Rust documentation and returns structured output with warning count.. It is categorised as a Execute tool in the Cargo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on doc? +

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

What risk level is doc? +

doc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit doc? +

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

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

doc is provided by the Cargo MCP server (@paretools/cargo). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Cargo

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.