4 tools. 0 can modify or destroy data without limits.
Read-only server. Low risk, but rate limits prevent runaway API costs.
Last updated:
Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.
Intercept sits between your agent and MCP Bench Router. 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-bench-router get_best_design_model:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The MCP Bench Router server is primarily read-only with 4 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.
4 tools across 1 categories: Read. 4 are read-only. 0 can modify, create, or delete data.
One line change. Instead of running the MCP Bench Router server directly, prefix it with Intercept: intercept -c mcp-bench-router.yaml -- npx -y @mcp-bench-router. Download a pre-built policy from policylayer.com/policies/mcp-bench-router and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init