8 tools. 4 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Destructive tools (deleteFileOrDir) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (moveFileOrDir, renameFileOrDir) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (wait) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
deleteFileOrDir:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
moveFileOrDir:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
checkFileOrDir:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Mcp Multitool server exposes 1 destructive tools including deleteFileOrDir. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Mcp Multitool server has 2 write tools including moveFileOrDir, renameFileOrDir. 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.
8 tools across 4 categories: Destructive, Execute, Read, Write. 4 are read-only. 4 can modify, create, or delete data.
One line change. Instead of running the Mcp Multitool server directly, prefix it with Intercept: intercept -c mcp-multitool.yaml -- npx -y @mcp-multitool. Download a pre-built policy from policylayer.com/policies/mcp-multitool and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.