Get detailed test run results including individual test case outcomes. Retrieves the run summary and a paginated list of test case results, with optional filtering by outcome status. WHEN TO USE: Phase 4, Step 13 — after syncing results, fetch this to get pass rate, failure details, and per-tes...
Part of the Invarium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call invarium_get_test_run 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_get_test_run 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_get_test_run:
rules:
- action: allowSee the full Invarium policy for all 19 tools.
Agents calling read-class tools like invarium_get_test_run 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.
Get detailed test run results including individual test case outcomes. Retrieves the run summary and a paginated list of test case results, with optional filtering by outcome status. WHEN TO USE: Phase 4, Step 13 — after syncing results, fetch this to get pass rate, failure details, and per-test-case outcomes. AFTER THIS: Combine with invarium_get_agent (for AQS score) to present a complete analytics summary. Then recommend next steps based on results: all passed → suggest sharing QA report; failures → suggest investigating and improving the agent. Args: agent_name: Name of the agent whose test run to retrieve. test_run_id: ID of the test run to retrieve results for. status: Filter results by status — "passed", "failed", "error", or "pending". If omitted, all results are returned. page: Page number for paginated results (default: 1). limit: Number of results per page (default: 20, max: 100).. 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_get_test_run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Invarium MCP server.
invarium_get_test_run 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_get_test_run 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_get_test_run. 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_get_test_run 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