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