zephyr_get_test_executions

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 100 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-get-test-executions.md

WHAT IT DOES

What zephyr_get_test_executions does on SmartBear MCP

AI agents call zephyr_get_test_executions to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`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
`testCase`	string	—	Test case key filter.
`startAtId`	number	—	Zero-indexed starting position for ID-based pagination.
`testCycle`	string	—	Test cycle key filter.
`projectKey`	string	—	Jira project key filter
`includeStepLinks`	boolean	—	If true, execution step issue links will be included in the response
`actualEndDateAfter`	string	—	Filter for 'Actual End Date' after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
`onlyLastExecutions`	boolean	—	If true, includes only the last execution of each test cycle item (test case), and all ad-hoc test executions.
`actualEndDateBefore`	string	—	Filter for 'Actual End Date' before the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
`jiraProjectVersionId`	number	—	Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.

Parameters from the server's own tool schema.

RISK

Why zephyr_get_test_executions is rated Low

This tool retrieves test execution data from Zephyr (Jira's test management integration) with filtering options. It has no side effects, does not create, modify, delete, or execute anything—it only queries and returns existing test execution records. The includeStepLinks parameter merely controls what fields are returned in the response, not what data is affected.

From the tool's definition Tool name contains 'get' and description states 'Get test executions with optional filters'. Parameters are all query filters (projectKey, testCycle, testCase, date ranges, boolean include flag) with no modification, deletion, or execution capabilities.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_get_test_executions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zephyr_get_test_executions, this is the rule to start with:

zephyr_get_test_executions Allowed

zephyr_get_test_executions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_get_test_executions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_get_test_executions call is checked against it from then on.

FAQ

Questions about zephyr_get_test_executions

What does the zephyr_get_test_executions tool do? +

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.

What parameters does zephyr_get_test_executions accept? +

zephyr_get_test_executions accepts 10 parameters: limit, testCase, startAtId, testCycle, projectKey, includeStepLinks, actualEndDateAfter, onlyLastExecutions, actualEndDateBefore, jiraProjectVersionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_get_test_executions? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_test_executions: 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 SmartBear MCP. Nothing to install.

What risk level is zephyr_get_test_executions? +

zephyr_get_test_executions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zephyr_get_test_executions? +

Yes. Add a rate_limit block to the zephyr_get_test_executions 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.

How do I block zephyr_get_test_executions completely? +

Set action: deny in the PolicyLayer 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.

What MCP server provides zephyr_get_test_executions? +

zephyr_get_test_executions is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →