List all test executions for a specific test cycle. Returns execution status, executedBy, actualEndDate for each test case in the cycle. Cloud only.
AI agents call list_executions_by_cycle 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 retrieves and lists test execution information from a specific test cycle without creating, modifying, deleting, or executing any operations. It is purely a data retrieval function, fitting the 'Read' category. The severity is low because exposing test execution metadata (status, executor, dates) has minimal blast radius and no irreversible consequences.
From the tool's definition Tool name 'list_executions_by_cycle' and description 'List all test executions for a specific test cycle. Returns execution status, executedBy, actualEndDate for each test case in the cycle.' indicate a query/retrieval operation with no modification or…
Attacks that exploit this kind of access
List all test executions for a specific test cycle. Returns execution status, executedBy, actualEndDate for each test case in the cycle. Cloud only. 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 list_executions_by_cycle: 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.
list_executions_by_cycle 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 list_executions_by_cycle 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 list_executions_by_cycle. 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.
list_executions_by_cycle 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 →