Get test execution IDs linked to a Jira issue.
AI agents call get_issue_link_test_executions 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 execution IDs associated with a Jira issue. It performs a read-only lookup operation with no capability to modify, delete, or execute actions. The blast radius is minimal—unauthorized access retrieves only metadata about existing test executions.
From the tool's definition Tool name 'get_issue_link_test_executions' and description 'Get test execution IDs linked to a Jira issue' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get test execution 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_executions: 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_executions 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_executions 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_executions. 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_executions 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 →