zephyr_create_test_case_steps

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 33 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-steps.md

WHAT IT DOES

What zephyr_create_test_case_steps does on SmartBear MCP

AI agents use zephyr_create_test_case_steps 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
`mode`	string	Yes	Valid values: `"APPEND"`, `"OVERWRITE"`. <br> `OVERWRITE` deletes and recreates the test steps and associated custom field values using the provided input. Atta
`items`	array	Yes	The list of test steps. Each step should be an object containing `inline` or `testCase`. They should only include one of these fields at a time.
`testCaseKey`	string	Yes	The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+

Parameters from the server's own tool schema.

RISK

Why zephyr_create_test_case_steps is rated Medium

This tool modifies test case definitions within Zephyr, a test management system. While OVERWRITE can delete existing steps, the operation is reversible (steps can be re-added), and the blast radius is limited to test case metadata rather than production data or financial systems.

From the tool's definition Tool description explicitly states it 'Create steps for a Test Case' and includes modes 'APPEND' (adds to existing) and 'OVERWRITE' (deletes all existing steps and replaces them). These are reversible modifications to test case data.

Risk signalsHigh parameter count (16 properties) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_create_test_case_steps Rate-limited

zephyr_create_test_case_steps 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_steps": {
      "limits": [
        {
          "counter": "zephyr_create_test_case_steps_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_steps call is checked against it from then on.

FAQ

Questions about zephyr_create_test_case_steps

What does the zephyr_create_test_case_steps tool do? +

Create steps for a Test Case in Zephyr. Supports inline step definitions or delegating execution to another test case (also known as 'call to test' via UI). Requires a mode: APPEND adds steps to the end of the existing list, OVERWRITE deletes all existing steps and replaces them with the provided ones. Always ask the user to choose between OVERWRITE or APPEND before calling this tool. Examples: 1. To the Test Case SA-T1, add steps that will test a login page. json { "testCaseKey": "SA-T1", "mode": "APPEND", "items": [ { "inline": { "description": "Navigate to the login page", "expectedResult": "Login page is displayed" } }, { "inline": { "description": "Enter valid credentials and click Submit", "expectedResult": "User is redirected to the dashboard" } } ] } Expected Output: The ID of the Test Steps resource and the API self URL to fetch it 2. To the Test Case MM2-T15, replace all existing steps with new ones that test the settings page for an Admin user. json { "testCaseKey": "MM2-T15", "mode": "OVERWRITE", "items": [ { "inline": { "description": "Open the settings page", "testData": "User role: Admin", "expectedResult": "Settings page is accessible" } }, { "inline": { "description": "Change the notification preference", "testData": "Preference: Email only", "expectedResult": "Notification preference is updated successfully" } } ] } Expected Output: The ID of the Test Steps resource and the API self URL to fetch it 3. To the Test Case SA-T1, add a step that reuses the steps from the Test Case PRJ-T42 json { "testCaseKey": "SA-T1", "mode": "APPEND", "items": [ { "testCase": { "testCaseKey": "PRJ-T42" } } ] } Expected Output: The ID of the Test Steps resource and the API self URL to fetch it. 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_steps accept? +

zephyr_create_test_case_steps accepts 3 parameters: mode, items, testCaseKey. Required: mode, items, testCaseKey. 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_steps? +

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

zephyr_create_test_case_steps 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_steps? +

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

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

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