5 tools. 4 can modify or destroy data without limits.
2 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (approvals, log-implementation) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Intercept sits between your agent and Spec Workflow. 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 @pimzino/spec-workflow-mcp approvals:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
spec-status:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Spec Workflow server exposes 2 destructive tools including approvals, log-implementation. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
5 tools across 3 categories: Destructive, Other, Read. 1 are read-only. 4 can modify, create, or delete data.
One line change. Instead of running the Spec Workflow server directly, prefix it with Intercept: intercept -c spec-workflow.yaml -- npx -y @@pimzino/spec-workflow-mcp. Download a pre-built policy from policylayer.com/policies/spec-workflow 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