zephyr_update_test_execution

// WHEN AI AGENTS USE THIS TOOL

AI agents use zephyr_update_test_execution to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON ZEPHYR_UPDATE_TEST_EXECUTION

Without a policy, an AI agent could call zephyr_update_test_execution repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

smartbear-mcp.yaml

tools:
  zephyr_update_test_execution:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full SmartBear MCP policy for all 243 tools.

// DETAILS

Tool Name zephyr_update_test_execution

Category Write

MCP Server SmartBear MCP MCP Server

Risk Level Medium

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive contract-testing_admin_delete_role Destructive contract-testing_admin_delete_team Destructive contract-testing_admin_delete_user Destructive contract-testing_admin_remove_role_from_user Destructive contract-testing_admin_remove_user_from_team Destructive contract-testing_admin_reset_roles Destructive contract-testing_delete_all_integrations

View all 243 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like zephyr_update_test_execution have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Firecrawl Web Scraping Server firecrawl_generate_llmstxt AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update

// RELATED READING

// FAQ

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.

How do I enforce a policy on zephyr_update_test_execution? +

Add a rule in your Intercept YAML policy under the tools section for zephyr_update_test_execution. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

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

How do I block zephyr_update_test_execution completely? +

Set action: deny in the Intercept 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 MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.