Display dependency tree.
AI agents call cargo_tree to retrieve information from Cargo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and displays the dependency tree of a Rust project. It has no side effects, does not modify any data, and cannot execute arbitrary code. It is equivalent to running 'cargo tree' which is a read-only introspection command.
From the tool's definition Display dependency tree
Attacks that exploit this kind of access
Display dependency tree. It is categorised as a Read tool in the Cargo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cargo MCP Server MCP server in PolicyLayer and add a rule for cargo_tree: 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_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cargo_tree 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_tree. 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_tree 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.
cargo_tree is one line of Cargo MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →