zephyr_update_test_case

// WHEN AI AGENTS USE THIS TOOL

AI agents use zephyr_update_test_case 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_CASE

Without a policy, an AI agent could call zephyr_update_test_case 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_case:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name zephyr_update_test_case

Category Write

MCP Server SmartBear MCP MCP Server

Risk Level Medium

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the zephyr_update_test_case tool do? +

Update an existing Test Case in Zephyr. This operation fetches the current test case and merges your updates with it to prevent accidental property deletion. Properties which are not included in the tool call will be left unchanged. To remove a property, set it to null explicitly. For fields that accept multiple values, such as `labels`, if the field is provided, it will override the previous values. For example, if `labels` is provided with the values `["label1", "label2"]`, the Test Case will now only have those two labels, and any previous labels will be removed. If you want to add a label, you would need to specify in the prompt the intention to add a label. **Examples:** 1. Update the name of the test case 'SA-T10' to 'Check axial pump' and objective to 'To ensure the axial pump can be enabled' ```json { "testCaseKey": "SA-T10", "name": "Check axial pump", "objective": "To ensure the axial pump can be enabled" } ``` Expected Output: The test case should be updated, but no output is expected. 2. Update the test case 'MM2-T1' by setting labels 'Regression','Performance' and 'Automated' and changing the priority to the one with id 2. ```json { "testCaseKey": "MM2-T1", "priority": { "id": 2 }, "labels": [ "Regression", "Performance", "Automated" ] } ``` Expected Output: The test case should be updated, but no output is expected. 3. Update test case 'SA-T5', by setting the custom field 'Build Number' to 20, 'Release Date' to '2020-01-01' and setting the Test Cases's estimated time to 3600000 milliseconds. ```json { "testCaseKey": "SA-T5", "estimatedTime": 3600000, "customFields": { "Build Number": 20, "Release Date": "2020-01-01" } } ``` Expected Output: The test case should be updated, but no output is expected. 4. Remove the component from test case 'SA-T20'. ```json { "testCaseKey": "SA-T20", "component": null } ``` Expected Output: The test case should be updated, but no output is expected. 5. Remove a specific custom field 'Pre-Condition(s)' from test case 'SA-T15' while keeping other custom fields intact ```json { "testCaseKey": "SA-T15", "customFields": { "Pre-Condition(s)": null, "Implemented": false } } ``` Expected Output: The test case 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_case? +

Add a rule in your Intercept YAML policy under the tools section for zephyr_update_test_case. 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_case? +

zephyr_update_test_case 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_case? +

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

Set action: deny in the Intercept policy for zephyr_update_test_case. 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_case? +

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

Enforce policies on SmartBear MCP