zephyr_create_test_case

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 122 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-case.md

WHAT IT DOES

What zephyr_create_test_case does on SmartBear MCP

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.

Parameter	Type	Required	Description
`name`	string	Yes
`labels`	array	—	Array of labels associated to this entity.
`ownerId`	object	—	Atlassian Account ID of the Jira user.
`folderId`	number	—	ID of a folder to place the entity within.
`objective`	object	—	A description of the objective.
`projectKey`	string	Yes	Jira project key.
`statusName`	string	—	The status name.
`componentId`	number	—	ID of a component from Jira.
`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
`precondition`	object	—	Any conditions that need to be met.
`priorityName`	string	—	The priority name.
`estimatedTime`	number	—	Estimated duration in milliseconds.

Parameters from the server's own tool schema.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_create_test_case 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_case, this is the rule to start with:

zephyr_create_test_case Rate-limited

zephyr_create_test_case 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_case": {
      "limits": [
        {
          "counter": "zephyr_create_test_case_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_case call is checked against it from then on.

FAQ

Questions about zephyr_create_test_case

What does the zephyr_create_test_case tool do? +

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<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 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. 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_case accept? +

zephyr_create_test_case accepts 12 parameters: name, labels, ownerId, folderId, objective, projectKey, statusName, componentId, customFields, precondition, priorityName, estimatedTime. Required: name, projectKey. 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_case? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_create_test_case: 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_case? +

zephyr_create_test_case 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_case? +

Yes. Add a rate_limit block to the zephyr_create_test_case 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_case completely? +

Set action: deny in the PolicyLayer policy for zephyr_create_test_case. 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_case? +

zephyr_create_test_case 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 →