Get detailed information about a specific test run
AI agents call get-test-run to retrieve information from QA Studio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries information about test runs without side effects. It falls squarely into the Read category as it only fetches existing data. The severity is low because viewing test run details poses minimal risk—it does not execute tests, modify configurations, delete data, or trigger external operations. An AI agent retrieving test run information cannot cause harm through this tool alone.
From the tool's definition Tool name 'get-test-run' and description 'Get detailed information about a specific test run' indicate retrieval of existing test run data with no modification, deletion, or execution of tests.
Attacks that exploit this kind of access
Get detailed information about a specific test run. It is categorised as a Read tool in the QA Studio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QA Studio MCP Server 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 QA Studio MCP Server. 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 QA Studio MCP Server MCP server (qastudio-dev/mcp-server). 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 →