32 tools. 17 can modify or destroy data without limits.
5 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (pylon_delete_account, pylon_delete_contact, pylon_delete_issue) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (pylon_create_account, pylon_create_contact, pylon_create_issue) 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 Pylon. 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 @pylon-mcp pylon_delete_account:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
pylon_create_account:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
pylon_get_account:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Pylon server exposes 5 destructive tools including pylon_delete_account, pylon_delete_contact, pylon_delete_issue. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Pylon server has 12 write tools including pylon_create_account, pylon_create_contact, pylon_create_issue. 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.
32 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 17 can modify, create, or delete data.
One line change. Instead of running the Pylon server directly, prefix it with Intercept: intercept -c io-github-justinbeckwith-pylon-mcp.yaml -- npx -y @pylon-mcp. Download a pre-built policy from policylayer.com/policies/io-github-justinbeckwith-pylon-mcp 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