zephyr_update_test_execution

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 81 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.md

WHAT IT DOES

What zephyr_update_test_execution does on SmartBear MCP

AI agents use zephyr_update_test_execution 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
`comment`	object	—	Comment added against overall test case execution.
`statusName`	string	—	The status name.
`assignedToId`	object	—	Atlassian Account ID of the Jira user.
`executedById`	object	—	Atlassian Account ID of the Jira user.
`actualEndDate`	string	—	The actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
`executionTime`	number	—	Actual test execution time in milliseconds.
`environmentName`	string	—	Environment assigned to the test case.
`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 is rated Medium

This tool creates or modifies data reversibly—it updates test execution records with new values. The operation is not destructive (doesn't delete or irreversibly overwrite), not financial, and not code execution. While it modifies state, the changes are limited to test metadata fields and can be reverted by subsequent updates.

From the tool's definition Tool name contains 'update' and description states 'Update an existing Test Execution in Zephyr. This operation only updates specified fields in the payload.' The examples show modifying statusName, environmentName, and execution timestamps.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_update_test_execution Rate-limited

zephyr_update_test_execution 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": {
      "limits": [
        {
          "counter": "zephyr_update_test_execution_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 call is checked against it from then on.

FAQ

Questions about zephyr_update_test_execution

What does the zephyr_update_test_execution tool do? +

Update an existing Test Execution in Zephyr. This operation only updates specified fields in the payload and ignores null or undefined values. Examples: 1. Update the status name to 'PASS' and the environment name to 'ENV-1' in the test execution 'SA-E40'. json { "testExecutionIdOrKey": "SA-E40", "statusName": "PASS", "environmentName": "ENV-1" } Expected Output: The test execution should be updated, but no output is expected. 2. Update execution time and actual end date for test execution id '1' (keep everything else unchanged). json { "testExecutionIdOrKey": "1", "executionTime": "2018-05-19T13:15:13Z", "actualEndDate": "2018-05-20T13:15:13Z" } Expected Output: The test execution should be updated, but no output is expected. 3. For test execution 'SA-E40', update the test executor and assignee to be the user with ID 10000. json { "testExecutionIdOrKey": "SA-E40", "executedById": "10000", "assignedToId": "10000" } Expected Output: The test execution should be updated, but no output is expected. 4. In test execution 'SA-E40', add a comment saying that this execution was updated via API. json { "testExecutionIdOrKey": "SA-E40", "comment": "execution updated via API" } Expected Output: The test execution should be updated, but no output is expected. 5. Remove the assigned user from test execution 'SA-E40'. json { "testExecutionIdOrKey": "SA-E40", "assignedToId": null } Expected Output: The test execution should be updated, 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 accept? +

zephyr_update_test_execution accepts 8 parameters: comment, statusName, assignedToId, executedById, actualEndDate, executionTime, environmentName, 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? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_update_test_execution: 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? +

zephyr_update_test_execution 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? +

Yes. Add a rate_limit block to the zephyr_update_test_execution 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 completely? +

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

zephyr_update_test_execution 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 →