# zephyr_create_test_execution Create a new Test Execution for a Test Case within a specific Test Cycle Parameters: - projectKey (string) *required*: Jira project key. - testCaseKey (string) *required*: Key of test case the execution applies to. NOTE: Test cases with call to test, parameters and test data are not supported. - testCycleKey (string) *required*: Key of test cycle the execution applies to. - statusName (string) *required*: The status name. - testScriptResults (array) - environmentName (string): Environment assigned to the test case. - actualEndDate (string): The actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' - executionTime (number): Actual test execution time in milliseconds. - executedById (string): Atlassian Account ID of the Jira user. - assignedToId (string): Atlassian Account ID of the Jira user. - comment (string): Comment added against overall test case execution. - 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 Passed execution for test case SA-T1 in cycle SA-R1 json { "projectKey": "SA", "testCaseKey": "SA-T1", "testCycleKey": "SA-R1", "statusName": "Pass" } Expected Output: The newly created Test Execution with execution details 2. Create a Failed execution with execution time, environment and comment json { "projectKey": "MM2", "testCaseKey": "MM2-T15", "testCycleKey": "MM2-R3", "statusName": "Fail", "environmentName": "Staging", "executionTime": 125000, "comment": "Step 3 failed due to timeout
Logs attached." } Expected Output: The newly created Test Execution including environment and timing information 3. Create execution with custom fields and assignment json { "projectKey": "SA", "testCaseKey": "SA-T5", "testCycleKey": "SA-R2", "statusName": "Pass", "executedById": "5b10ac8d82e05b22cc7d4ef5", "assignedToId": "5b10ac8d82e05b22cc7d4ef6", "actualEndDate": "2026-02-17T10:15:30Z", "customFields": { "Execution Build": "1.0.3", "Tested Browser": "Chrome", "Execution Date": "2026-02-17" } } Expected Output: The newly created Test Execution including custom field values Agent View of the PolicyLayer registry record for `zephyr_create_test_execution`. HTML page: https://policylayer.com/tools/smartbear-mcp/zephyr-create-test-execution ## Facts - Tool: `zephyr_create_test_execution` - 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 (4 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `comment` | object | no | Comment added against overall test case execution. | | `projectKey` | string | yes | Jira project key. | | `statusName` | string | yes | The status name. | | `testCaseKey` | string | yes | Key of test case the execution applies to. NOTE: Test cases with call to test, parameters and test data are not supported. | | `assignedToId` | object | no | Atlassian Account ID of the Jira user. | | `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 | | `executedById` | object | no | Atlassian Account ID of the Jira user. | | `testCycleKey` | string | yes | Key of test cycle the execution applies to. | | `actualEndDate` | string | no | The actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z' | | `executionTime` | number | no | Actual test execution time in milliseconds. | | `environmentName` | string | no | Environment assigned to the test case. | | `testScriptResults` | array | no | | 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_execution", "arguments": { "projectKey": "", "statusName": "", "testCaseKey": "", "testCycleKey": "" } } } ``` ## Why zephyr_create_test_execution is rated Medium This tool creates a new test execution record within a test management system (Zephyr/Jira). It modifies state by adding a new entity but does not delete, execute arbitrary code, move money, or trigger external operations with uncontrolled side effects. From the tool's own definition: "Tool name is 'zephyr_create_test_execution' and description states 'Create a new Test Execution for a Test Case' — the verb 'Create' and 'create' in the description indicate data creation." Risk signals: High parameter count (15 properties) ## Use case AI agents use zephyr_create_test_execution 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_execution": { "limits": [ { "counter": "zephyr_create_test_execution_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