11 tools. 4 can modify or destroy data without limits.
2 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (clear_history, delete_table_row) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (update_table_row) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (run_query) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
clear_history:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
update_table_row:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get_active_queries:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Devtools server exposes 2 destructive tools including clear_history, delete_table_row. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Devtools server has 1 write tools including update_table_row. 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.
11 tools across 4 categories: Destructive, Execute, Read, Write. 7 are read-only. 4 can modify, create, or delete data.
One line change. Instead of running the Devtools server directly, prefix it with Intercept: intercept -c devtools.yaml -- npx -y @@spooky-sync/devtools-mcp. Download a pre-built policy from policylayer.com/policies/devtools 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.