9 tools. 9 can modify or destroy data without limits.
9 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (tsc) 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, esbuild, lerna) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Build. 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 @paretools/build tsc:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
The Build server has 1 write tools including tsc. 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.
9 tools across 2 categories: Execute, Write. 0 are read-only. 9 can modify, create, or delete data.
One line change. Instead of running the Build server directly, prefix it with Intercept: intercept -c io-github-dave-london-build.yaml -- npx -y @@paretools/build. Download a pre-built policy from policylayer.com/policies/io-github-dave-london-build 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