zephyr_update_test_cycle

// WHEN AI AGENTS USE THIS TOOL

AI agents use zephyr_update_test_cycle 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_CYCLE

Without a policy, an AI agent could call zephyr_update_test_cycle 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_cycle:
    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_cycle

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_cycle tool do? +

Update an existing Test Cycle in Zephyr. This operation fetches the current test cycle and merges your updates with it to prevent accidental property deletion. To remove a property, set it to null explicitly. The plannedStartDate and plannedEndDate fields cannot be cleared **Examples:** 1. Update the name of the test cycle 'SA-R40' to 'Sprint 1 Regression - Updated' and set description. ```json { "testCycleIdOrKey": "SA-R40", "name": "Sprint 1 Regression - Updated", "description": "Updated regression scope for Sprint 1" } ``` Expected Output: The test cycle should be updated, but no output is expected. 2. Update planned dates for test cycle id '1' (keep everything else unchanged). ```json { "testCycleIdOrKey": "1", "plannedStartDate": "2018-05-19T13:15:13Z", "plannedEndDate": "2018-05-20T13:15:13Z" } ``` Expected Output: The test cycle should be updated, but no output is expected. 3. Change folder and status for test cycle 'SA-R40' by setting folder id and status id. ```json { "testCycleIdOrKey": "SA-R40", "folder": { "id": 100006 }, "status": { "id": 10000 } } ``` Expected Output: The test cycle should be updated, but no output is expected. 4. Update custom fields on test cycle 'SA-R40' while keeping other custom fields intact. ```json { "testCycleIdOrKey": "SA-R40", "customFields": { "Build Number": 20, "Release Date": "2020-01-01" } } ``` Expected Output: The test cycle should be updated, but no output is expected. 5. Remove the owner from test cycle 'SA-R40'. ```json { "testCycleIdOrKey": "SA-R40", "owner": null } ``` Expected Output: The test cycle should be updated, but no output is expected. 6. Remove a specific custom field 'Pre-Condition(s)' from test cycle 'SA-R40' while keeping other custom fields intact. ```json { "testCycleIdOrKey": "SA-R40", "customFields": { "Pre-Condition(s)": null, "Implemented": false } } ``` Expected Output: The test cycle 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_cycle? +

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

zephyr_update_test_cycle 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_cycle? +

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

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

zephyr_update_test_cycle 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