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