zephyr_get_test_cases
Get details of test cases in Zephyr Parameters: - projectKey (string): Jira project key filter - folderId (number): Folder ID filter - limit (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. ...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-cases.md
What zephyr_get_test_cases does on SmartBear MCP
AI agents call zephyr_get_test_cases 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 |
|---|---|---|---|
limit | 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 |
folderId | number | — | Folder ID filter |
startAtId | number | — | Zero-indexed starting position for ID-based pagination. |
projectKey | string | — | Jira project key filter |
updatedAfter | string | — | Filter only entities updated after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z' |
Parameters from the server's own tool schema.
Why zephyr_get_test_cases is rated Low
This tool retrieves and queries test case data from Zephyr with no side effects. It is a straightforward read operation that returns test case details based on filtering and pagination parameters. No data is created, modified, deleted, or executed.
From the tool's definition Tool name "zephyr_get_test_cases" and description "Get details of test cases in Zephyr" indicate data retrieval. Parameters include filters (projectKey, folderId) and pagination (limit) with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs zephyr_get_test_cases 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_cases, this is the rule to start with:
zephyr_get_test_cases 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_cases call is checked against it from then on.
Questions about zephyr_get_test_cases
Get details of test cases in Zephyr Parameters: - projectKey (string): Jira project key filter - folderId (number): Folder ID filter - limit (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 server may enforce a lower limit than requested, depending on resource availability or other internal constraints. If this happens, the result set may be truncated. Always check the limit value in the response to confirm how many results were actually returned. (default: 10) - startAtId (number): Zero-indexed starting position for ID-based pagination. (default: 0) - updatedAfter (string): Filter only entities updated after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z' Examples: 1. Get the first 10 Test Cases json { "limit": 10, "startAtId": 1 } Expected Output: The first 10 Test Cases with their details 2. Get any Test Case json { "limit": 1 } Expected Output: One Test Case with its details 3. Get five Test Cases starting from the ID 123 json { "limit": 5, "startAtId": 123 } Expected Output: Five Test Cases starting from the ID 123 with their details 4. Get one Test Case from the project PROJ json { "projectKey": "PROJ", "limit": 1 } Expected Output: One Test Case from project PROJ with its details 5. Get one Test Case from the folder with ID 123 json { "folderId": 123, "limit": 1 } Expected Output: One Test Case from folder with ID 123 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_cases accepts 5 parameters: limit, folderId, startAtId, projectKey, updatedAfter. 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_cases: 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_cases 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_cases 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_cases. 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_cases 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