Search for test runs using a query. Supports filtering by projectKey and/or folder path. On Cloud, only returns cycles in the exact folder (not sub-folders). Use folder_id for direct numeric ID lookup (skips path resolution).
AI agents call search_test_runs to retrieve information from Zephyr Scale MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves test run data from Zephyr Scale based on filter criteria (projectKey, folder path, folder_id). It performs no modifications, deletions, or side effects—it is a pure read operation. Severity is low because unauthorized access to test run metadata poses minimal risk compared to destructive or financial actions.
From the tool's definition Tool name 'search_test_runs' and description 'Search for test runs using a query' indicate data retrieval. The description specifies filtering and lookup capabilities with no mention of modification, deletion, or execution of code/operations.
Attacks that exploit this kind of access
Search for test runs using a query. Supports filtering by projectKey and/or folder path. On Cloud, only returns cycles in the exact folder (not sub-folders). Use folder_id for direct numeric ID lookup (skips path resolution). It is categorised as a Read tool in the Zephyr Scale MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for search_test_runs: 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 Zephyr Scale MCP Server. Nothing to install.
search_test_runs 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 search_test_runs 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 search_test_runs. 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.
search_test_runs is provided by the Zephyr Scale MCP Server MCP server (milo0821/zephyr_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 →