Get test result(s) by test run ID.
AI agents call get_test_result to retrieve information from QIT 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 test results from existing test runs. There is no indication it modifies, deletes, or executes any operations—it simply queries and returns data. The narrow scope (lookup by ID) and passive nature (reading cached/stored results) make this a straightforward Read category tool with low severity risk, as misuse would only expose test data rather than alter systems or execute arbitrary code.
From the tool's definition Tool name 'get_test_result' and description 'Get test result(s) by test run ID' indicate a query/retrieval operation. The verb 'Get' and the read-only nature of retrieving previously-generated test results confirms this is a Read action with no side effects.
Attacks that exploit this kind of access
Get test result(s) by test run ID. It is categorised as a Read tool in the QIT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QIT MCP Server MCP server in PolicyLayer and add a rule for get_test_result: 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 QIT MCP Server. Nothing to install.
get_test_result 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_result 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_result. 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_result is provided by the QIT MCP Server MCP server (woocommerce/qit-mcp). 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 →