# zephyr_update_test_cycle 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. Agent View of the PolicyLayer registry record for `zephyr_update_test_cycle`. HTML page: https://policylayer.com/tools/smartbear-mcp/zephyr-update-test-cycle ## Facts - Tool: `zephyr_update_test_cycle` - 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: 12 (1 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | number | no | The ID of the entity | | `key` | string | no | Unique key of the test cycle | | `name` | string | no | | | `owner` | object | no | Atlassian Account ID of the Jira user. | | `folder` | object | no | ID and link to the folder resource. | | `status` | object | no | ID and link to the status resource. | | `project` | object | no | ID and link relative to Zephyr project. | | `description` | object | no | Description outlining the scope. | | `customFields` | object | no | Multi-line text fields support HTML and should denote new lines with the \ tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jir | | `plannedEndDate` | object | no | The planned end date of the test cycle. This field cannot be blank. Setting it as null or excluding it from the request will leave the field values unchanged. I | | `plannedStartDate` | object | no | Planned start date of the test cycle. This field cannot be blank. Setting it as null or excluding it from the request will leave the field values unchanged. ISO | | `testCycleIdOrKey` | string | yes | The ID or key of the test cycle. | 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_cycle", "arguments": { "testCycleIdOrKey": "" } } } ``` ## Why zephyr_update_test_cycle is rated Medium This tool creates or modifies data (test cycle metadata) in a reversible manner. Updates can be undone by applying contrary updates. It does not delete data irreversibly, execute arbitrary code, move money, or trigger external operations. The blast radius is limited to test cycle metadata within Zephyr, making it a Write operation at medium severity. From the tool's own definition: "Tool description states 'Update an existing Test Cycle in Zephyr' and 'merges your updates with it' and 'set it to null explicitly' — clear modification operations. Example shows updating 'name' and 'description' fields." Risk signals: Accepts file system path (folder) · High parameter count (17 properties) ## Use case AI agents use zephyr_update_test_cycle 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_cycle": { "limits": [ { "counter": "zephyr_update_test_cycle_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