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 fi...
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_execution_steps 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_execution_steps 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_execution_steps:
rules:
- action: allowSee the full SmartBear MCP policy for all 147 tools.
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.
Add a rule in your Intercept YAML policy under the tools section for zephyr_get_test_execution_steps. 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_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 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_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 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