zephyr_get_test_case
Get details of test case specified by key in Zephyr Parameters: - testCaseKey (string) *required*: The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+ Examples: 1. Get the test case with key 'SA-T10' json { "testCaseKey": "SA-T10" } Expected Output: The test case with its de...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-case.md
What zephyr_get_test_case does on SmartBear MCP
AI agents call zephyr_get_test_case 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 |
|---|---|---|---|
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.
Why zephyr_get_test_case is rated Low
This tool retrieves and returns metadata about a test case without modifying, executing, or deleting any data. It takes a test case key as input and returns the test case details. This is a classic read operation with minimal risk – the worst that could happen is unauthorized visibility into test case information, which is low-severity information disclosure.
From the tool's definition Tool name and description: 'Get details of test case specified by key in Zephyr' – the verb 'Get' and the action of retrieving test case details indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs zephyr_get_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_get_test_case, this is the rule to start with:
zephyr_get_test_case is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_get_test_case call is checked against it from then on.
Questions about zephyr_get_test_case
Get details of test case specified by key in Zephyr Parameters: - testCaseKey (string) *required*: The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+ Examples: 1. Get the test case with key 'SA-T10' json { "testCaseKey": "SA-T10" } Expected Output: The test case with its details 2. Get the test case with key 'MM2-T1' json { "testCaseKey": "MM2-T1" } Expected Output: The test case with its details. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
zephyr_get_test_case accepts 1 parameter: testCaseKey. Required: testCaseKey. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_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.
zephyr_get_test_case is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zephyr_get_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.
Set action: deny in the PolicyLayer policy for zephyr_get_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.
zephyr_get_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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue