zephyr_get_test_execution_steps
Get details of test execution steps in Zephyr Examples: 1. Get the first 10 test execution steps for test execution with ID 1 json { "testExecutionIdOrKey": "1", "maxResults": 10, "startAt": 0 } Expected Output: The first 10 test execution steps with their details 2. Get the first 10 test executi...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-execution-steps.md
What zephyr_get_test_execution_steps does on SmartBear MCP
AI agents call zephyr_get_test_execution_steps 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 |
|---|---|---|---|
startAt | number | — | Zero-indexed starting position. Should be a multiple of maxResults. |
maxResults | 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 |
testDataRowNumber | number | — | The id of the test data row to retrieve. |
testExecutionIdOrKey | string | Yes | The ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+ |
Parameters from the server's own tool schema.
Why zephyr_get_test_execution_steps is rated Low
This tool retrieves and queries test execution step data from Zephyr without any side effects. It has no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an AI agent could only read test execution metadata that it already has access credentials to view.
From the tool's definition Tool name includes 'get' and description states 'Get details of test execution steps'. Parameters are testExecutionIdOrKey, maxResults, and startAt—all indicative of retrieval with pagination.
Attacks that exploit this kind of access
The rule that runs zephyr_get_test_execution_steps 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_execution_steps, this is the rule to start with:
zephyr_get_test_execution_steps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_get_test_execution_steps call is checked against it from then on.
Questions about zephyr_get_test_execution_steps
Get details of test execution steps in Zephyr Examples: 1. Get the first 10 test execution steps for test execution with ID 1 json { "testExecutionIdOrKey": "1", "maxResults": 10, "startAt": 0 } Expected Output: The first 10 test execution steps with their details 2. Get the first 10 test execution steps for test execution with key 'SA-E1' json { "testExecutionIdOrKey": "SA-E1", "maxResults": 10, "startAt": 0 } Expected Output: The first 10 test execution steps with their details 3. Get any test execution step for test execution with key 'SA-E1' json { "testExecutionIdOrKey": "SA-E1", "maxResults": 1 } Expected Output: One test execution step with its details 4. Get five test execution steps starting from the 7th test execution step for test execution with key 'SA-E1' json { "testExecutionIdOrKey": "SA-E1", "maxResults": 5, "startAt": 6 } Expected Output: The 7th to the 11th test execution steps with their details 5. Get test execution steps from the test data row 1 from test execution with key 'SA-E1' json { "testExecutionIdOrKey": "SA-E1", "testDataRowNumber": 1, "maxResults": 10, "startAt": 0 } Expected Output: Test execution steps for the specified test data row. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
zephyr_get_test_execution_steps accepts 4 parameters: startAt, maxResults, testDataRowNumber, testExecutionIdOrKey. Required: testExecutionIdOrKey. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_test_execution_steps: 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.
zephyr_get_test_execution_steps 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_execution_steps 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 zephyr_get_test_execution_steps. 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_execution_steps 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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue