Install or update the Invarium tracer library in .invarium/. Returns a curl command for the LLM to execute. The tracer file is downloaded directly from the MCP server's /api/tracer endpoint, avoiding passing 1200 lines through the conversation context. WHEN TO USE: Phase 3, Step 10 — when the u...
Part of the Invarium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use invarium_setup_tracing to create or modify resources in Invarium. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call invarium_setup_tracing repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Invarium.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
invarium_setup_tracing:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Invarium policy for all 19 tools.
Agents calling write-class tools like invarium_setup_tracing have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Install or update the Invarium tracer library in .invarium/. Returns a curl command for the LLM to execute. The tracer file is downloaded directly from the MCP server's /api/tracer endpoint, avoiding passing 1200 lines through the conversation context. WHEN TO USE: Phase 3, Step 10 — when the user is ready to run tests. AFTER THIS: Tell the user the tracer is ready. Then write the test_run.py script using the test cases from invarium_get_tests.. It is categorised as a Write tool in the Invarium MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for invarium_setup_tracing. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Invarium MCP server.
invarium_setup_tracing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the invarium_setup_tracing rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for invarium_setup_tracing. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
invarium_setup_tracing is provided by the Invarium MCP server (invarium-ai/invarium). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept