zephyr_update_test_case

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-update-test-case.md

WHAT IT DOES

What zephyr_update_test_case does on SmartBear MCP

AI agents use zephyr_update_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
`id`	number	—	The ID of the entity
`key`	string	—	The test case key
`name`	string	—
`owner`	object	—	Atlassian Account ID of the Jira user.
`folder`	object	—	The ID of the folder, to remove folder set it's value to null
`labels`	array	—	Array of labels associated to this entity.
`status`	object	—	ID and link to the status resource.
`project`	object	—	ID and link relative to Zephyr project.
`priority`	object	—	ID and link to the priority resource.
`component`	object	—	ID and link to the Jira component resource.
`objective`	object	—	A description of the objective.
`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_update_test_case is rated Medium

This tool creates or modifies data reversibly, matching the Write category. It updates test case properties and can override field values, but these changes are not permanent deletions and can be reversed by subsequent updates.

From the tool's definition Tool description explicitly states "Update an existing Test Case in Zephyr" and "merges your updates with it". The operation modifies test case data reversibly through property updates and overwrites of multi-value fields like labels.

Risk signalsAccepts file system path (folder) · High parameter count (21 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_update_test_case Rate-limited

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

FAQ

Questions about zephyr_update_test_case

What does the zephyr_update_test_case tool do? +

Update an existing Test Case in Zephyr. This operation fetches the current test case and merges your updates with it to prevent accidental property deletion. Properties which are not included in the tool call will be left unchanged. To remove a property, set it to null explicitly. For fields that accept multiple values, such as labels, if the field is provided, it will override the previous values. For example, if labels is provided with the values ["label1", "label2"], the Test Case will now only have those two labels, and any previous labels will be removed. If you want to add a label, you would need to specify in the prompt the intention to add a label. Examples: 1. Update the name of the test case 'SA-T10' to 'Check axial pump' and objective to 'To ensure the axial pump can be enabled' json { "testCaseKey": "SA-T10", "name": "Check axial pump", "objective": "To ensure the axial pump can be enabled" } Expected Output: The test case should be updated, but no output is expected. 2. Update the test case 'MM2-T1' by setting labels 'Regression','Performance' and 'Automated' and changing the priority to the one with id 2. json { "testCaseKey": "MM2-T1", "priority": { "id": 2 }, "labels": [ "Regression", "Performance", "Automated" ] } Expected Output: The test case should be updated, but no output is expected. 3. Update test case 'SA-T5', by setting the custom field 'Build Number' to 20, 'Release Date' to '2020-01-01' and setting the Test Cases's estimated time to 3600000 milliseconds. json { "testCaseKey": "SA-T5", "estimatedTime": 3600000, "customFields": { "Build Number": 20, "Release Date": "2020-01-01" } } Expected Output: The test case should be updated, but no output is expected. 4. Remove the component from test case 'SA-T20'. json { "testCaseKey": "SA-T20", "component": null } Expected Output: The test case should be updated, but no output is expected. 5. Remove a specific custom field 'Pre-Condition(s)' from test case 'SA-T15' while keeping other custom fields intact json { "testCaseKey": "SA-T15", "customFields": { "Pre-Condition(s)": null, "Implemented": false } } Expected Output: The test case should be updated, but no output is expected. 6. Remove test case from folder json { "testCaseKey": "SA-T15", "folder": null } Expected Output: The test case should be updated, but no output is expected. 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_update_test_case accept? +

zephyr_update_test_case accepts 12 parameters: id, key, name, owner, folder, labels, status, project, priority, component, objective, 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_update_test_case? +

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

zephyr_update_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_update_test_case? +

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

Set action: deny in the PolicyLayer policy for zephyr_update_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_update_test_case? +

zephyr_update_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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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