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