// MCP TOOL REFERENCE

CARGO TOOLS

12 tools from the Cargo MCP Server, categorised by risk level.

READ TOOLS

check Runs cargo check (type check without full build) and returns structured diagnostics. Faster than build for error checking. 2/5 test Runs cargo test and returns structured test results (name, status, pass/fail counts). 2/5

WRITE TOOLS

add Adds dependencies to a Rust project and returns structured output. WARNING: may execute untrusted code. 3/5 update Updates dependencies in the lock file. Optionally updates a single package. 3/5

DESTRUCTIVE TOOLS

remove Removes dependencies from a Rust project and returns structured output. 5/5

EXECUTE TOOLS

audit Runs cargo audit and returns structured vulnerability data. 3/5 build Runs cargo build and returns structured diagnostics (file, line, code, severity, message). 4/5 clippy Runs cargo clippy and returns structured lint diagnostics. 3/5 doc Generates Rust documentation and returns structured output with warning count. 3/5 fmt Checks or fixes Rust formatting and returns structured output. 3/5 run Runs a cargo binary and returns structured output (exit code, stdout, stderr). 4/5 tree Displays the dependency tree for a Rust project. 3/5

// FAQ

How many tools does the Cargo MCP server have? +

The Cargo MCP server exposes 12 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Cargo tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Cargo server.

What risk categories do Cargo tools fall into? +

Cargo tools are categorised as Read (2), Write (2), Destructive (1), Execute (7). Each category has a recommended default policy.

Enforce policies on Cargo

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →