51 tools. 32 can modify or destroy data without limits.
9 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (batch_delete_tasks, delete_folder, delete_project) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (add_task_notification, append_task_note, batch_complete_tasks) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
batch_delete_tasks:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
add_task_notification:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get_database_summary:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Omnifocus server exposes 9 destructive tools including batch_delete_tasks, delete_folder, delete_project. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Omnifocus server has 23 write tools including add_task_notification, append_task_note, batch_complete_tasks. 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.
51 tools across 3 categories: Destructive, Read, Write. 19 are read-only. 32 can modify, create, or delete data.
One line change. Instead of running the Omnifocus server directly, prefix it with Intercept: intercept -c omnifocus.yaml -- npx -y @omnifocus-mcp-server. Download a pre-built policy from policylayer.com/policies/omnifocus 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.