Remove a link between two Jira issues
AI agents call remove_issue_link to permanently remove resources in Jira — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes an issue link in Jira. Unlike soft modifications, removing a link cannot be undone through normal means, making it a destructive operation. Misuse by an AI agent could silently sever important issue relationships (e.g., blocking dependencies, duplicate links) across projects, with potentially high blast radius if done in bulk or on critical issues.
From the tool's definition 'Remove a link between two Jira issues' — removing a link is an irreversible deletion of the relationship between issues
Attacks that exploit this kind of access
Remove a link between two Jira issues. It is categorised as a Destructive tool in the Jira MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jira MCP server in PolicyLayer and add a rule for remove_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 Jira. Nothing to install.
remove_issue_link is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_issue_link is provided by the Jira MCP server (taraskhust/jira-mcp-server). 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 →