zephyr_create_test_cycle

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 102 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What zephyr_create_test_cycle does on SmartBear MCP

AI agents use zephyr_create_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
`name`	string	Yes
`ownerId`	object	—	Atlassian Account ID of the Jira user.
`folderId`	number	—	ID of a folder to place the entity within.
`projectKey`	string	Yes	Jira project key.
`statusName`	string	—	The status name.
`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`	string	—	The planned end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
`plannedStartDate`	string	—	Planned start date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
`jiraProjectVersion`	number	—	Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.

Parameters from the server's own tool schema.

RISK

Why zephyr_create_test_cycle is rated Medium

This tool creates new test management artifacts (test cycles) in Jephyr, which is a reversible write operation. It doesn't execute tests or code (Execute), delete data (Destructive), move money (Financial), or merely retrieve data (Read). The impact is confined to creating structured test planning data within a project management system, making it a Write-category risk.

From the tool's definition Tool creates a new Test Cycle resource in Zephyr with required parameters 'projectKey' and 'name', along with optional metadata like description, dates, version, status, and folder association.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_create_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_create_test_cycle, this is the rule to start with:

zephyr_create_test_cycle Rate-limited

zephyr_create_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_create_test_cycle": {
      "limits": [
        {
          "counter": "zephyr_create_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_create_test_cycle call is checked against it from then on.

FAQ

Questions about zephyr_create_test_cycle

What does the zephyr_create_test_cycle tool do? +

Create a new Test Cycle in Zephyr specified project Parameters: - projectKey (string) *required*: Jira project key. - name (string) *required* - description (string): Description outlining the scope. - plannedStartDate (string): Planned start date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' - plannedEndDate (string): The planned end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' - jiraProjectVersion (number): Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects. - statusName (string): The status name. - folderId (number): ID of a folder to place the entity within. - ownerId (string): Atlassian Account ID of the Jira user. - customFields (record<string, any>): 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 Jira User Account IDs. Examples: 1. Create a Test Cycle in project SA to ensure that the axial pump can be enabled json { "projectKey": "SA", "name": "Check axial pump", "description": "Ensure the axial pump can be enabled" } Expected Output: The newly created Test Cycle with its details and key 2. Create a Test Cycle to ensure that the axial pump can be enabled. The test cycle should be in project MM2, have status 'In Progress', and be planned from 2026-03-01 to 2026-03-10 json { "projectKey": "MM2", "name": "Check axial pump", "description": "Ensure the axial pump can be enabled", "statusName": "In Progress", "plannedStartDate": "2026-03-01T00:00:00Z", "plannedEndDate": "2026-03-10T00:00:00Z" } Expected Output: The newly created Test Cycle with its details and key 3. Create a Test Cycle for verifying strength of the axial pump with custom field 'Axial pump strength' having value '5' in project SA json { "projectKey": "SA", "name": "Check axial pump strength", "description": "Make sure the axial pump operates at the required strength", "customFields": { "Axial pump strength": 5 } } Expected Output: The newly created Test Cycle with its details and key 4. Create a Test Cycle in project MM2 to verify the performance of the axial pump with Jira Project Version ID 10001, owner Atlassian Account ID '12', in folder with ID 18 json { "projectKey": "MM2", "name": "Check axial pump performance", "description": "Ensure the axial pump performs within acceptable limits", "jiraProjectVersion": 10001, "ownerId": "12", "folderId": 18 } Expected Output: The newly created Test Cycle with its details and key. 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_create_test_cycle accept? +

zephyr_create_test_cycle accepts 10 parameters: name, ownerId, folderId, projectKey, statusName, description, customFields, plannedEndDate, plannedStartDate, jiraProjectVersion. Required: name, projectKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_create_test_cycle? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_create_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_create_test_cycle? +

zephyr_create_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_create_test_cycle? +

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

Set action: deny in the PolicyLayer policy for zephyr_create_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_create_test_cycle? +

zephyr_create_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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