zephyr_get_issue_link_test_cases
Get test cases linked to a Jira issue in Zephyr Parameters: - issueKey (string) *required*: The key of the Jira issue Examples: 1. Check which test cases are linked to Jira issue PROJ-123 json { "issueKey": "PROJ-123" } Expected Output: The List of test cases linked to Jira issue PROJ-123 with th...
This record as markdown: /tools/smartbear-mcp/zephyr-get-issue-link-test-cases.md
What zephyr_get_issue_link_test_cases does on SmartBear MCP
AI agents call zephyr_get_issue_link_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 |
|---|---|---|---|
issueKey | string | Yes | The key of the Jira issue |
Parameters from the server's own tool schema.
Why zephyr_get_issue_link_test_cases is rated Low
This is a straightforward query operation that fetches and returns existing data about test case associations. There is no creation, modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an agent could retrieve information about linked test cases but cannot alter configurations, delete data, or cause irreversible changes.
From the tool's definition Tool retrieves test cases linked to a Jira issue ("Get test cases linked") and returns a list with no indication of modification, creation, or deletion. The verb "get" and output description "The List of test cases" confirm data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs zephyr_get_issue_link_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_issue_link_test_cases, this is the rule to start with:
zephyr_get_issue_link_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_issue_link_test_cases call is checked against it from then on.
Questions about zephyr_get_issue_link_test_cases
Get test cases linked to a Jira issue in Zephyr Parameters: - issueKey (string) *required*: The key of the Jira issue Examples: 1. Check which test cases are linked to Jira issue PROJ-123 json { "issueKey": "PROJ-123" } Expected Output: The List of test cases linked to Jira issue PROJ-123 with their keys and versions. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
zephyr_get_issue_link_test_cases accepts 1 parameter: issueKey. Required: issueKey. 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_issue_link_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_issue_link_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_issue_link_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_issue_link_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_issue_link_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