# zephyr_create_test_case Create a new Test Case in Zephyr specified project Parameters: - projectKey (string) *required*: Jira project key. - name (string) *required* - objective (string): A description of the objective. - precondition (string): Any conditions that need to be met. - estimatedTime (number): Estimated duration in milliseconds. - componentId (number): ID of a component from Jira. - priorityName (string): The priority name. - 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. - labels (array): Array of labels associated to this entity. - 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 Case in project SA to ensure that the axial pump can be enabled json { "projectKey": "SA", "name": "Check axial pump", "objective": "Ensure the axial pump can be enabled" } Expected Output: The newly created Test Case with its details and key 2. Create a Test Case to ensure that the axial pump can be enabled. The test should be in project MM2, have labels 'automated' and 'mcp', and priority 'High' json { "projectKey": "MM2", "name": "Check axial pump", "objective": "Ensure the axial pump can be enabled", "labels": [ "automated", "mcp" ], "priorityName": "High" } Expected Output: The newly created Test Case with its details and key 3. Create a Test Case 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", "objective": "Make sure the axial pump operates at the required strength", "customFields": { "Axial pump strength": 5 } } Expected Output: The newly created Test Case with its details and key 4. Create a Test Case in project MM2 to verify the performance of the axial pump with Jira component having ID 10001, Jira owner having ID 10057 in folder 'Pumps' json { "projectKey": "MM2", "name": "Check axial pump performance", "objective": "Ensure the axial pump performs within acceptable limits", "componentId": 10001, "ownerJiraUserId": 10057, "folderId": 18 } Expected Output: The newly created Test Case with its details and key Agent View of the PolicyLayer registry record for `zephyr_create_test_case`. HTML page: https://policylayer.com/tools/smartbear-mcp/zephyr-create-test-case ## Facts - Tool: `zephyr_create_test_case` - 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 (2 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `name` | string | yes | | | `labels` | array | no | Array of labels associated to this entity. | | `ownerId` | object | no | Atlassian Account ID of the Jira user. | | `folderId` | number | no | ID of a folder to place the entity within. | | `objective` | object | no | A description of the objective. | | `projectKey` | string | yes | Jira project key. | | `statusName` | string | no | The status name. | | `componentId` | number | no | ID of a component from Jira. | | `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 | | `precondition` | object | no | Any conditions that need to be met. | | `priorityName` | string | no | The priority name. | | `estimatedTime` | number | no | Estimated duration in milliseconds. | 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_case", "arguments": { "name": "", "projectKey": "" } } } ``` ## Why zephyr_create_test_case is rated Medium This tool creates new test case entities in Zephyr/Jira, which is a reversible write operation. It modifies project data by adding new records but does not delete, execute arbitrary code, or move money. Severity is medium because misuse could create numerous test cases or associate them with wrong projects/owners, requiring cleanup, but the operation is not destructive or irreversible. From the tool's own definition: "Tool name contains 'create' and description states 'Create a new Test Case in Zephyr specified project'. Parameters allow specifying test case properties (name, objective, precondition, owner, etc.), confirming data creation." Risk signals: High parameter count (12 properties) ## Use case AI agents use zephyr_create_test_case 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_case": { "limits": [ { "counter": "zephyr_create_test_case_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