zephyr_get_test_case_steps

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What zephyr_get_test_case_steps does on SmartBear MCP

AI agents call zephyr_get_test_case_steps to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`startAt`	number	—	Zero-indexed starting position. Should be a multiple of maxResults.
`maxResults`	number	—	Specifies the maximum number of results to return in a single call. The default value is 10, and the maximum value that can be requested is 1000. Note that the
`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_get_test_case_steps is rated Low

This tool retrieves or queries test case step details from Zephyr with no side effects or data modification. The operation is purely informational, fitting the Read category. Severity is low as misuse would only expose test data, not cause irreversible harm or financial impact.

From the tool's definition Tool name 'zephyr_get_test_case_steps' and description 'Get details of test case steps in Zephyr' indicate a retrieval operation. Examples show pagination parameters (maxResults, startAt) used to query and fetch test case step data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_get_test_case_steps Allowed

zephyr_get_test_case_steps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_get_test_case_steps": {}
  }
}

ALLOW ONLY 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_get_test_case_steps call is checked against it from then on.

FAQ

Questions about zephyr_get_test_case_steps

What does the zephyr_get_test_case_steps tool do? +

Get details of test case steps in Zephyr Examples: 1. Get the first 10 test case steps for test case with key 'SA-T1' json { "testCaseKey": "SA-T1", "maxResults": 10, "startAt": 0 } Expected Output: The first 10 test case steps with their details 2. Get any test case step for test case with key 'SA-T1' json { "testCaseKey": "SA-T1", "maxResults": 1 } Expected Output: One test case step with its details 3. Get five test case steps starting from the 7th test case step of the list for test case with key 'SA-T1' json { "testCaseKey": "SA-T1", "maxResults": 5, "startAt": 6 } Expected Output: The 7th to the 11th test case steps with their details. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does zephyr_get_test_case_steps accept? +

zephyr_get_test_case_steps accepts 3 parameters: startAt, maxResults, 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_get_test_case_steps? +

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

zephyr_get_test_case_steps is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zephyr_get_test_case_steps? +

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

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

zephyr_get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →