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 use...
Part of the Invarium server.
Free to start. No card required.
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. PolicyLayer'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.
{
"version": "1",
"default": "deny",
"tools": {
"invarium_setup_tracing": {
"limits": [
{
"counter": "invarium_setup_tracing_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Invarium policy for all 19 tools.
These attack patterns abuse exactly the kind of access invarium_setup_tracing gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Invarium MCP server in PolicyLayer and add a rule for invarium_setup_tracing: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Invarium. Nothing to install.
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 PolicyLayer 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 PolicyLayer 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Invarium tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.