1 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.
web_search_exa:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Exa Web Search Server server is primarily read-only with 1 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.
1 tools across 1 categories: Read. 1 are read-only. 0 can modify, create, or delete data.
One line change. Instead of running the Exa Web Search Server server directly, prefix it with Intercept: intercept -c aditya002p-mcp-server.yaml -- npx -y @aditya002p/mcp-server. Download a pre-built policy from policylayer.com/policies/aditya002p-mcp-server and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.