zephyr_create_test_cycle

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.

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

zephyr_create_test_cycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

Set action: deny in the Intercept 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.

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