AI agents call launch_list_test_results to retrieve information from Testops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists test result data from a launch. It is a read-only query returning paginated rows of result information with no side effects.
From the tool's definition Flat paginated test results for a launch (rows: id, name, testCaseId, status, duration, etc.)
Attacks that exploit this kind of access
Flat paginated test results for a launch (rows: id, name, testCaseId, status, duration, etc.). It is categorised as a Read tool in the Testops MCP Server, which means it retrieves data without modifying state.
Register the Testops MCP server in PolicyLayer and add a rule for launch_list_test_results: 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 Testops. Nothing to install.
launch_list_test_results 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 launch_list_test_results 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 launch_list_test_results. 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.
launch_list_test_results is provided by the Testops MCP server (@syn7xx/testops-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 →