Generate documentation for a Rust project.
AI agents invoke cargo_doc to trigger actions in Cargo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes the `cargo doc` command, which compiles and generates documentation artifacts. While not destructive (documentation generation is reversible via cleanup) and not a read-only query, it triggers external code execution.
From the tool's definition Tool description states "Generate documentation for a Rust project." The name and description indicate execution of `cargo doc`, which is a code generation tool that compiles documentation from source code.
Attacks that exploit this kind of access
Generate documentation for a Rust project. It is categorised as a Execute tool in the Cargo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cargo MCP Server MCP server in PolicyLayer and add a rule for cargo_doc: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Cargo MCP Server. Nothing to install.
cargo_doc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cargo_doc rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for cargo_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.
cargo_doc is provided by the Cargo MCP Server MCP server (seemethere/cargo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →