Get test run details (status, dates, test case count).
AI agents call get_test_run to retrieve information from PolarionMcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only information about test run metadata (status, dates, test case count) from Polarion ALM. There is no indication it modifies data, executes arbitrary code, deletes records, or commits financial transactions. The action is purely informational query, fitting the Read category. Low severity because misuse would only expose testing metadata without affecting system integrity or operations.
From the tool's definition Tool name is 'get_test_run' and description states it 'Get test run details (status, dates, test case count)' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get test run details (status, dates, test case count). It is categorised as a Read tool in the PolarionMcp MCP Server, which means it retrieves data without modifying state.
Register the Polarion MCP server in PolicyLayer and add a rule for get_test_run: 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 PolarionMcp. Nothing to install.
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 get_test_run 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 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.
get_test_run is provided by the Polarion MCP server (mmerah/polarionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →