# zephyr_update_test_execution 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. Agent View of the PolicyLayer registry record for `zephyr_update_test_execution`. HTML page: https://policylayer.com/tools/smartbear-mcp/zephyr-update-test-execution ## Facts - Tool: `zephyr_update_test_execution` - Server: SmartBear MCP (`SmartBear/smartbear-mcp`) — https://policylayer.com/tools/smartbear-mcp.md - Homepage: https://github.com/SmartBear/smartbear-mcp - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 8 (1 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `comment` | object | no | Comment added against overall test case execution. | | `statusName` | string | no | The status name. | | `assignedToId` | object | no | Atlassian Account ID of the Jira user. | | `executedById` | object | no | Atlassian Account ID of the Jira user. | | `actualEndDate` | string | no | The actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | | `executionTime` | number | no | Actual test execution time in milliseconds. | | `environmentName` | string | no | 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. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "zephyr_update_test_execution", "arguments": { "testExecutionIdOrKey": "" } } } ``` ## 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 own 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 signals: Bulk/mass operation — affects multiple targets ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches SmartBear MCP: ```json { "version": "1", "default": "deny", "tools": { "zephyr_update_test_execution": { "limits": [ { "counter": "zephyr_update_test_execution_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on SmartBear MCP (239) - `collaborator_delete_collaborator_remote_system_configuration` — Destructive — https://policylayer.com/tools/smartbear-mcp/collaborator-delete-collaborator-remote-system-configuration.md - `contract-testing_admin_delete_role` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-delete-role.md - `contract-testing_admin_delete_team` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-delete-team.md - `contract-testing_admin_delete_user` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-delete-user.md - `contract-testing_admin_remove_role_from_user` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-remove-role-from-user.md - `contract-testing_admin_remove_user_from_team` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-remove-user-from-team.md - `contract-testing_admin_reset_roles` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-admin-reset-roles.md - `contract-testing_delete_all_integrations` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-all-integrations.md - `contract-testing_delete_branch` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-branch.md - `contract-testing_delete_environment` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-environment.md - `contract-testing_delete_integration` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-integration.md - `contract-testing_delete_pacticipant` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-pacticipant.md - `contract-testing_delete_secret` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-secret.md - `contract-testing_delete_webhook` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-delete-webhook.md - `contract-testing_regenerate_api_token` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-regenerate-api-token.md - `contract-testing_remove_label_from_pacticipant` — Destructive — https://policylayer.com/tools/smartbear-mcp/contract-testing-remove-label-from-pacticipant.md - `reflect_cancel_suite_execution` — Destructive — https://policylayer.com/tools/smartbear-mcp/reflect-cancel-suite-execution.md - `reflect_delete_previous_step` — Destructive — https://policylayer.com/tools/smartbear-mcp/reflect-delete-previous-step.md - `swagger_delete_portal_product` — Destructive — https://policylayer.com/tools/smartbear-mcp/swagger-delete-portal-product.md - `swagger_delete_table_of_contents` — Destructive — https://policylayer.com/tools/smartbear-mcp/swagger-delete-table-of-contents.md - `collaborator_reviewservice_action` — Execute — https://policylayer.com/tools/smartbear-mcp/collaborator-reviewservice-action.md - `collaborator_test_collaborator_remote_system_configuration_connection` — Execute — https://policylayer.com/tools/smartbear-mcp/collaborator-test-collaborator-remote-system-configuration-connection.md - `contract-testing_execute_webhook` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-execute-webhook.md - `contract-testing_generate_pact_tests` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-generate-pact-tests.md - `contract-testing_review_pact_tests` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-review-pact-tests.md - `contract-testing_test_execute_webhooks` — Execute — https://policylayer.com/tools/smartbear-mcp/contract-testing-test-execute-webhooks.md - `reflect_add_prompt_step` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-add-prompt-step.md - `reflect_connect_to_session` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-connect-to-session.md - `reflect_execute_suite` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-execute-suite.md - `reflect_run_test` — Execute — https://policylayer.com/tools/smartbear-mcp/reflect-run-test.md - …and 209 more: https://policylayer.com/tools/smartbear-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=smartbear-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/smartbear-mcp