# 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): 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 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 Agent View of the PolicyLayer registry record for `zephyr_create_test_cycle`. HTML page: https://policylayer.com/tools/smartbear-mcp/zephyr-create-test-cycle ## Facts - Tool: `zephyr_create_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: 10 (2 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `name` | string | yes | | | `ownerId` | object | no | Atlassian Account ID of the Jira user. | | `folderId` | number | no | ID of a folder to place the entity within. | | `projectKey` | string | yes | Jira project key. | | `statusName` | string | no | The status name. | | `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` | string | no | The planned end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | | `plannedStartDate` | string | no | Planned start date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | | `jiraProjectVersion` | number | no | Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects. | 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_create_test_cycle", "arguments": { "name": "", "projectKey": "" } } } ``` ## 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 own 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 signals: High parameter count (10 properties) ## Use case 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. ## 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_create_test_cycle": { "limits": [ { "counter": "zephyr_create_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