zephyr_create_test_script

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 31 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-script.md

WHAT IT DOES

What zephyr_create_test_script does on SmartBear MCP

AI agents use zephyr_create_test_script 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
`text`	string	—
`type`	string	—	Test scripts can be written in plain text or BDD format. The BDD type supports remote execution on a build system via API plugin. Supported Keywords for BDD: G
`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_script is rated Medium

This tool creates (writes) new test script data in Zephyr test cases. It modifies the test case by adding a new script artifact, but the operation is reversible (scripts can be deleted or modified).

From the tool's definition Tool creates a new Test Script in a Zephyr Test Case with parameters testCaseKey, type, and text. The description explicitly states 'Create a new Test Script' which is a write operation that adds new data to the system.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_create_test_script Rate-limited

zephyr_create_test_script 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_script": {
      "limits": [
        {
          "counter": "zephyr_create_test_script_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_script call is checked against it from then on.

FAQ

Questions about zephyr_create_test_script

What does the zephyr_create_test_script tool do? +

Create a new Test Script of the types Plain Text or BDD in a Zephyr Test Case. Examples: 1. Create a plain text test script for test case SA-T1 to verify that the axial pump can be enabled json { "testCaseKey": "SA-T1", "type": "plain", "text": "1. Navigate to Pump Settings</br>2. Enable Axial Pump</br>3. Verify pump status is 'Active'" } Expected Output: The created test script metadata including its id and self link 2. Create a BDD test script for test case MM2-T15 to validate axial pump activation json { "testCaseKey": "MM2-T15", "type": "bdd", "text": "Given the axial pump is installed\nWhen the user enables the axial pump\nThen the pump status should be Active" } Expected Output: The created test script metadata including its id and self link 3. Create a BDD test script for test case QA-T100 for axial pump performance validation json { "testCaseKey": "QA-T100", "type": "bdd", "text": "Given the system is running\nWhen the axial pump operates under load\nThen performance metrics should remain within thresholds" } Expected Output: The created test script metadata including its id and self link. 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_script accept? +

zephyr_create_test_script accepts 3 parameters: text, type, testCaseKey. Required: 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_script? +

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

zephyr_create_test_script 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_script? +

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

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

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