Show your current plan usage and remaining limits. Displays how many agents, test generations, simulation runs, and API keys you've used this month vs your plan limits. WHEN TO USE: Before Phase 2 (test generation) to check if the user has enough quota. Also useful when the user asks about thei...
Part of the Invarium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call invarium_usage to retrieve information from Invarium without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though invarium_usage only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
invarium_usage:
rules:
- action: allowSee the full Invarium policy for all 19 tools.
Agents calling read-class tools like invarium_usage have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Show your current plan usage and remaining limits. Displays how many agents, test generations, simulation runs, and API keys you've used this month vs your plan limits. WHEN TO USE: Before Phase 2 (test generation) to check if the user has enough quota. Also useful when the user asks about their plan or limits. The generate_tests tool checks this automatically, but showing it to the user proactively helps them plan their testing budget. No parameters required. Returns usage for the authenticated user.. It is categorised as a Read tool in the Invarium MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for invarium_usage. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Invarium MCP server.
invarium_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the invarium_usage 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_usage. 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_usage 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