zephyr_update_test_cycle

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-update-test-cycle.md

WHAT IT DOES

What zephyr_update_test_cycle does on SmartBear MCP

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.

Parameter	Type	Required	Description
`id`	number	—	The ID of the entity
`key`	string	—	Unique key of the test cycle
`name`	string	—
`owner`	object	—	Atlassian Account ID of the Jira user.
`folder`	object	—	ID and link to the folder resource.
`status`	object	—	ID and link to the status resource.
`project`	object	—	ID and link relative to Zephyr project.
`description`	object	—	Description outlining the scope.
`customFields`	object	—	Multi-line text fields support HTML and should denote new lines with the \<br\> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jir
`plannedEndDate`	object	—	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	—	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.

RISK

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 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 signalsAccepts file system path (folder) · High parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_update_test_cycle safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zephyr_update_test_cycle, this is the rule to start with:

zephyr_update_test_cycle Rate-limited

zephyr_update_test_cycle stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_update_test_cycle": {
      "limits": [
        {
          "counter": "zephyr_update_test_cycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_update_test_cycle call is checked against it from then on.

FAQ

Questions about zephyr_update_test_cycle

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.

What parameters does zephyr_update_test_cycle accept? +

zephyr_update_test_cycle accepts 12 parameters: id, key, name, owner, folder, status, project, description, customFields, plannedEndDate, plannedStartDate, testCycleIdOrKey. Required: testCycleIdOrKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_update_test_cycle? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_update_test_cycle: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SmartBear MCP. Nothing to install.

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 PolicyLayer 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 PolicyLayer 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 server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →