Create a link between a test case and a Jira issue.
AI agents use create_test_case_issue_link to create or update resources in Zephyr Scale MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zephyr Scale MCP Server environment.
This tool creates a new relationship/association between a test case and a Jira issue, which is a data modification operation. It does not execute external workflows, delete data irreversibly, or handle financial transactions. While it could be misused to spam or tamper with Jira issue tracking, the impact is limited to creating associations that are typically reversible.
From the tool's definition Tool name 'create_test_case_issue_link' and description 'Create a link between a test case and a Jira issue' indicate a create/modify operation that establishes a relationship between two entities. This is reversible (links can be deleted/unlinked).
Attacks that exploit this kind of access
Create a link between a test case and a Jira issue. It is categorised as a Write tool in the Zephyr Scale MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for create_test_case_issue_link: 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.
create_test_case_issue_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_test_case_issue_link 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 create_test_case_issue_link. 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.
create_test_case_issue_link 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 →