8 tools. 7 can modify or destroy data without limits.
7 write tools that can modify data. Rate limits recommended.
Last updated:
Execute tools (inverspec_phase_0_inventory, inverspec_phase_1_architecture, inverspec_phase_3_features) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
inverspec_phase_2_data_model:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Inverspec 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.
8 tools across 2 categories: Execute, Read. 1 are read-only. 7 can modify, create, or delete data.
One line change. Instead of running the Inverspec server directly, prefix it with Intercept: intercept -c inverspec.yaml -- npx -y @mcp-server-inverspec. Download a pre-built policy from policylayer.com/policies/inverspec and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.