Open a test result in the default web browser and return the report URL.
AI agents invoke open_test_result to trigger actions in QIT MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (opening the default web browser) rather than simply reading or returning data. While it also returns a URL, the act of launching a browser process is an Execute-category side effect. The blast radius is low since it only opens a browser tab to view a test report.
From the tool's definition Open a test result in the default web browser
Attacks that exploit this kind of access
Open a test result in the default web browser and return the report URL. It is categorised as a Execute tool in the QIT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the QIT MCP Server MCP server in PolicyLayer and add a rule for open_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.
open_test_result is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_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 open_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.
open_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 →