23 tools. 8 can modify or destroy data without limits.
3 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (d1_database_delete, kv_namespace_delete, r2_bucket_delete) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (d1_database_create, kv_namespace_create, kv_namespace_update) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and Cloudflare. 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 @cloudflare/mcp-server-cloudflare d1_database_delete:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
d1_database_create:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
accounts_list:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Cloudflare server exposes 3 destructive tools including d1_database_delete, kv_namespace_delete, r2_bucket_delete. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Cloudflare server has 5 write tools including d1_database_create, kv_namespace_create, kv_namespace_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.
23 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 8 can modify, create, or delete data.
One line change. Instead of running the Cloudflare server directly, prefix it with Intercept: intercept -c cloudflare.yaml -- npx -y @@cloudflare/mcp-server-cloudflare. Download a pre-built policy from policylayer.com/policies/cloudflare and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init