27 tools. 20 can modify or destroy data without limits.
20 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (api, gist-create, issue-close) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (run-list, run-rerun, run-view) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Github. 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/github api:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
discussion-list:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Github server has 17 write tools including api, gist-create, issue-close. 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.
27 tools across 3 categories: Execute, Read, Write. 7 are read-only. 20 can modify, create, or delete data.
One line change. Instead of running the Github server directly, prefix it with Intercept: intercept -c io-github-dave-london-github.yaml -- npx -y @@paretools/github. Download a pre-built policy from policylayer.com/policies/io-github-dave-london-github 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