Delete an issue link by id.
AI agents call jira_remove_issue_link to permanently remove resources in Jiraxmcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes (deletes) existing issue links in Jira, an action that cannot be reversed. While the blast radius is narrower than deleting entire issues (jira_delete_issue), removing issue links still destroys data relationships permanently. This justifies the Destructive category and high severity due to potential workflow disruption and loss of traceability if critical issue dependencies are severed.
From the tool's definition Tool name contains 'remove' and description explicitly states 'Delete an issue link by id' — deletion of issue links is irreversible and cannot be undone.
Attacks that exploit this kind of access
Delete an issue link by id. It is categorised as a Destructive tool in the Jiraxmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jirax MCP server in PolicyLayer and add a rule for jira_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 Jiraxmcp. Nothing to install.
jira_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 jira_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 jira_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.
jira_remove_issue_link is provided by the Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). 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 →