zephyr_create_test_execution

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 124 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-create-test-execution.md

WHAT IT DOES

What zephyr_create_test_execution does on SmartBear MCP

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.

Parameter	Type	Required	Description
`comment`	object	—	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	—	Atlassian Account ID of the Jira user.
`customFields`	object	—	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 Jir
`executedById`	object	—	Atlassian Account ID of the Jira user.
`testCycleKey`	string	Yes	Key of test cycle the execution applies to.
`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.
`environmentName`	string	—	Environment assigned to the test case.
`testScriptResults`	array	—

Parameters from the server's own tool schema.

RISK

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 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 signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_create_test_execution safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zephyr_create_test_execution, this is the rule to start with:

zephyr_create_test_execution Rate-limited

zephyr_create_test_execution stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_create_test_execution": {
      "limits": [
        {
          "counter": "zephyr_create_test_execution_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_create_test_execution call is checked against it from then on.

FAQ

Questions about zephyr_create_test_execution

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.

What parameters does zephyr_create_test_execution accept? +

zephyr_create_test_execution accepts 12 parameters: comment, projectKey, statusName, testCaseKey, assignedToId, customFields, executedById, testCycleKey, actualEndDate, executionTime, environmentName, testScriptResults. Required: projectKey, statusName, testCaseKey, testCycleKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_create_test_execution? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_create_test_execution: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SmartBear MCP. Nothing to install.

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 PolicyLayer 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 PolicyLayer 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 server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →