Remove a link between two Jira tickets. Fetches the issue to find the link ID automatically.
AI agents call jira_unlink_tickets to permanently remove resources in Jira MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a link between Jira tickets is a destructive operation because it permanently deletes an established relationship. While the tickets themselves remain intact, the link metadata is lost and may not be trivially recoverable. This is more severe than a Write operation because it irreversibly removes existing data rather than creating or modifying it.
From the tool's definition 'Remove a link between two Jira tickets' — the operation removes/deletes an existing relationship between tickets, which is not easily reversible without knowing the original link type and configuration
Attacks that exploit this kind of access
Remove a link between two Jira tickets. Fetches the issue to find the link ID automatically. It is categorised as a Destructive tool in the Jira MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_unlink_tickets: 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 MCP Server. Nothing to install.
jira_unlink_tickets 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 jira_unlink_tickets 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 jira_unlink_tickets. 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.
jira_unlink_tickets is provided by the Jira MCP Server MCP server (rui-branco/jira-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 →