Cargo

12 tools. 10 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

10 can modify or destroy data
2 read-only
12 tools total
Read (2) Write / Execute (9) Destructive / Financial (1)

Destructive tools (remove) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (add, update) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (audit, build, clippy) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Cargo. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @paretools/cargo
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
Deny destructive operations
remove:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
add:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
check:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent delete data through the Cargo MCP server? +

Yes. The Cargo server exposes 1 destructive tools including remove. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Cargo? +

The Cargo server has 2 write tools including add, update. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Cargo MCP server expose? +

12 tools across 4 categories: Destructive, Execute, Read, Write. 2 are read-only. 10 can modify, create, or delete data.

How do I add Intercept to my Cargo setup? +

One line change. Instead of running the Cargo server directly, prefix it with Intercept: intercept -c io-github-dave-london-cargo.yaml -- npx -y @@paretools/cargo. Download a pre-built policy from policylayer.com/policies/io-github-dave-london-cargo and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.