Get test plan IDs linked to a Jira issue.
AI agents call get_issue_link_test_plans to retrieve information from Zephyr Scale MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves test plan identifiers associated with a Jira issue. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It is a read-only data retrieval operation with minimal security risk — an agent misusing it could only access information already linked to the issue.
From the tool's definition Tool name 'get_issue_link_test_plans' begins with 'get_', indicating retrieval of existing data. Description states 'Get test plan IDs linked to a Jira issue' — a query operation that retrieves linked test plans without modifying or deleting data.
Attacks that exploit this kind of access
Get test plan IDs linked to a Jira issue. It is categorised as a Read tool in the Zephyr Scale MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for get_issue_link_test_plans: 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 Zephyr Scale MCP Server. Nothing to install.
get_issue_link_test_plans 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 get_issue_link_test_plans 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 get_issue_link_test_plans. 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.
get_issue_link_test_plans is provided by the Zephyr Scale MCP Server MCP server (metquay/zephyr-scale-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →