17 tools. 11 can modify or destroy data without limits.
11 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (add_ticket_comment, add_time_worked, complete_weekly_checklist) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and MCP Request-tracker. 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 @mcp-request-tracker-crunchtools add_ticket_comment:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
Cross-Platform:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The MCP Request-tracker server has 11 write tools including add_ticket_comment, add_time_worked, complete_weekly_checklist. 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. 6 are read-only. 11 can modify, create, or delete data.
One line change. Instead of running the MCP Request-tracker server directly, prefix it with Intercept: intercept -c mcp-request-tracker.yaml -- npx -y @mcp-request-tracker-crunchtools. Download a pre-built policy from policylayer.com/policies/mcp-request-tracker and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init