18 tools. 16 can modify or destroy data without limits.
16 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (tool_base64_decode, tool_base64_encode, tool_csv_to_json) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (tool_cron_parse, tool_url_parse) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Developer Utilities. 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 @aparajithn/agent-utils-mcp-new tool_base64_decode:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
tool_json_validate:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Developer Utilities server has 14 write tools including tool_base64_decode, tool_base64_encode, tool_csv_to_json. 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.
18 tools across 3 categories: Execute, Read, Write. 2 are read-only. 16 can modify, create, or delete data.
One line change. Instead of running the Developer Utilities server directly, prefix it with Intercept: intercept -c aparajithn-agent-utils-mcp-new.yaml -- npx -y @aparajithn/agent-utils-mcp-new. Download a pre-built policy from policylayer.com/policies/aparajithn-agent-utils-mcp-new 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