Delete a JIRA issue.
AI agents call jira_delete_issue to permanently remove resources in MCP JIRA Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a JIRA issue permanently removes it from the system and cannot be undone. This is an irreversible operation that destroys data, fitting the Destructive category. Severity is high because deletion of tracked work items impacts team visibility, audit trails, and project history, though the blast radius is typically contained to a single issue unless used in bulk.
From the tool's definition Tool name: 'jira_delete_issue'. Description: 'Delete a JIRA issue.' The verb 'delete' and action of removing an issue from JIRA indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a JIRA issue. It is categorised as a Destructive tool in the MCP JIRA Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP JIRA Server MCP server in PolicyLayer and add a rule for jira_delete_issue: 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 MCP JIRA Server. Nothing to install.
jira_delete_issue 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_delete_issue 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_delete_issue. 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_delete_issue is provided by the MCP JIRA Server MCP server (tarangbhavsar/mcp-jira-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 →