zephyr_get_test_case_links
Get all links (issue links and web links) associated with a test case 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 all links associated with the test case with key 'SA-T10' json { "testCaseKey":...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-case-links.md
What zephyr_get_test_case_links does on SmartBear MCP
AI agents call zephyr_get_test_case_links 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_links is rated Low
This tool queries and returns metadata about test case links without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no side effects, fitting the Read category with low severity since unauthorized access would only expose reference links, not sensitive credentials or controls.
From the tool's definition Tool retrieves 'all links (issue links and web links) associated with a test case' — a query operation with no modification or execution of code. The verb 'Get' and the retrieval-only nature indicate a read operation.
Attacks that exploit this kind of access
The rule that runs zephyr_get_test_case_links 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_links, this is the rule to start with:
zephyr_get_test_case_links 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_links call is checked against it from then on.
Questions about zephyr_get_test_case_links
Get all links (issue links and web links) associated with a test case 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 all links associated with the test case with key 'SA-T10' json { "testCaseKey": "SA-T10" } Expected Output: The links (issue links and web links) associated with the test case. 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_links 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_links: 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_links 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_links 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_links. 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_links 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