zephyr_create_test_execution

// WHEN AI AGENTS USE THIS TOOL

AI agents use zephyr_create_test_execution to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON ZEPHYR_CREATE_TEST_EXECUTION

Without a policy, an AI agent could call zephyr_create_test_execution repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

smartbear-mcp.yaml

tools:
  zephyr_create_test_execution:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name zephyr_create_test_execution

Category Write

MCP Server SmartBear MCP MCP Server

Risk Level Medium

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the zephyr_create_test_execution tool do? +

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

How do I enforce a policy on zephyr_create_test_execution? +

Add a rule in your Intercept YAML policy under the tools section for zephyr_create_test_execution. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is zephyr_create_test_execution? +

zephyr_create_test_execution 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_execution? +

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

How do I block zephyr_create_test_execution completely? +

Set action: deny in the Intercept policy for zephyr_create_test_execution. 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_execution? +

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

Enforce policies on SmartBear MCP