17 tools. 9 can modify or destroy data without limits.
9 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (add_issue_comment, create_branch, create_issue) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
add_issue_comment:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get_file_contents:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The GitHub API MCP Server server has 9 write tools including add_issue_comment, create_branch, create_issue. 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.
17 tools across 2 categories: Read, Write. 8 are read-only. 9 can modify, create, or delete data.
One line change. Instead of running the GitHub API MCP Server server directly, prefix it with Intercept: intercept -c renantrendt-reference-servers.yaml -- npx -y @renantrendt/reference-servers. Download a pre-built policy from policylayer.com/policies/renantrendt-reference-servers and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.