Get test executions with optional filters **Parameters:** - projectKey (string): Jira project key filter - testCycle (string): Test cycle key filter. - testCase (string): Test case key filter. - actualEndDateAfter (string): Filter for 'Actual End Date' after the given time. Format: yyyy-MM-dd'T'...
High parameter count (10 properties); Single-target operation
Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call zephyr_get_test_executions to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though zephyr_get_test_executions only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
zephyr_get_test_executions:
rules:
- action: allowSee the full SmartBear MCP policy for all 147 tools.
Get test executions with optional filters **Parameters:** - projectKey (string): Jira project key filter - testCycle (string): Test cycle key filter. - testCase (string): Test case key filter. - actualEndDateAfter (string): Filter for 'Actual End Date' after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z' - actualEndDateBefore (string): Filter for 'Actual End Date' before the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z' - includeStepLinks (boolean): If true, execution step issue links will be included in the response (default: false) - jiraProjectVersionId (number): Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects. - onlyLastExecutions (boolean): If true, includes only the last execution of each test cycle item (test case), and all ad-hoc test executions. (default: false) - limit (number): Specifies the maximum number of results to return in a single call. The default value is 10, and the maximum value that can be requested is 1000. Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints. If this happens, the result set may be truncated. Always check the limit value in the response to confirm how many results were actually returned. (default: 10) - startAtId (number): Zero-indexed starting position for ID-based pagination. (default: 0) **Examples:** 1. Get the first 10 test executions ```json { "limit": 10, "startAtId": 0 } ``` Expected Output: The first 10 test executions with their details 2. Get 5 test executions for the project PROJ ```json { "projectKey": "PROJ", "limit": 5 } ``` Expected Output: Up to 5 test executions for project PROJ 3. Get some test executions that finished after 01/Jan/2024 ```json { "actualEndDateAfter": "2024-01-01T00:00:00Z" } ``` Expected Output: Test executions that ended after 2024-01-01 4. Get test executions with step links included ```json { "includeStepLinks": true } ``` Expected Output: Test executions with step links included. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for zephyr_get_test_executions. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.
zephyr_get_test_executions 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 zephyr_get_test_executions rule in your Intercept 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 Intercept policy for zephyr_get_test_executions. 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.
zephyr_get_test_executions is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept