zephyr_update_test_execution_steps

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-update-test-execution-steps.md

WHAT IT DOES

What zephyr_update_test_execution_steps does on SmartBear MCP

AI agents use zephyr_update_test_execution_steps to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

Parameter	Type	Required	Description
`steps`	array	—
`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.

RISK

Why zephyr_update_test_execution_steps is rated Medium

The tool creates or modifies test execution data reversibly by updating step statuses and results in Zephyr. This is a Write operation—the changes can be undone or corrected by subsequent updates. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).

From the tool's definition Tool name includes 'update' and description states 'This operation updates the provided steps with their execution status and actual results.' The examples show modification of test execution records with statusName and actualResult fields.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_update_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_update_test_execution_steps, this is the rule to start with:

zephyr_update_test_execution_steps Rate-limited

zephyr_update_test_execution_steps stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_update_test_execution_steps": {
      "limits": [
        {
          "counter": "zephyr_update_test_execution_steps_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_update_test_execution_steps call is checked against it from then on.

FAQ

Questions about zephyr_update_test_execution_steps

What does the zephyr_update_test_execution_steps tool do? +

Update test steps for a given Test Execution in Zephyr. This operation updates the provided steps with their execution status and actual results. Only the fields included in the request will be modified. Examples: 1. Mark the status of all steps in the test execution 'SA-E1' as 'Pass'. Set the actual result of step 1 to 'Dashboard widgets loaded correctly' and step 2 to 'Navigation menu responded correctly to user interactions'. json { "testExecutionIdOrKey": "SA-E1", "steps": [ { "statusName": "Pass", "actualResult": "Dashboard widgets loaded correctly" }, { "statusName": "Pass", "actualResult": "Navigation menu responded correctly to user interactions" } ] } Expected Output: Test steps are updated successfully, but no output is expected. 2. Update only the status of step 2 in test execution 'SA-E5' to 'Fail'. Do not modify any other fields. json { "testExecutionIdOrKey": "SA-E5", "steps": [ {}, { "statusName": "Fail" } ] } Expected Output: The test execution steps are updated, but no output is expected. 3. Update only the actual results of the steps in test execution '10'. Set the actual result of step 1 to 'API returned 500 error' and step 2 actual result to 'API returned 200 success' json { "testExecutionIdOrKey": "10", "steps": [ { "actualResult": "API returned 500 error" }, { "actualResult": "API returned 200 success" } ] } Expected Output: Test steps are updated successfully, but no output is expected. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does zephyr_update_test_execution_steps accept? +

zephyr_update_test_execution_steps accepts 2 parameters: steps, testExecutionIdOrKey. Required: testExecutionIdOrKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_update_test_execution_steps? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_update_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.

What risk level is zephyr_update_test_execution_steps? +

zephyr_update_test_execution_steps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zephyr_update_test_execution_steps? +

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

How do I block zephyr_update_test_execution_steps completely? +

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

What MCP server provides zephyr_update_test_execution_steps? +

zephyr_update_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.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →