7 tools. 2 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Destructive tools (threadmap_reset) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Execute tools (threadmap_track) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Threadmap. 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 @threadmap-mcp threadmap_reset:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
threadmap_branch_context:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Threadmap server exposes 1 destructive tools including threadmap_reset. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
7 tools across 3 categories: Destructive, Execute, Read. 5 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the Threadmap server directly, prefix it with Intercept: intercept -c io-github-advertflair-threadmap-mcp.yaml -- npx -y @threadmap-mcp. Download a pre-built policy from policylayer.com/policies/io-github-advertflair-threadmap-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