Delete an issue from Jira
AI agents call jira_delete_issue to permanently remove resources in Jira MCP Integration — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of Jira issues cannot be undone and permanently removes project data, comments, attachments, and history. This is a destructive operation that could cause significant loss of project information if misused by an AI agent. The high severity reflects the potential for accidentally deleting critical issues, losing audit trails, or disrupting project workflows.
From the tool's definition Tool name is 'jira_delete_issue' and description states 'Delete an issue from Jira'. The verb 'delete' and the action of removing an issue from a project management system is irreversible.
Attacks that exploit this kind of access
Delete an issue from Jira. It is categorised as a Destructive tool in the Jira MCP Integration MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jira MCP Integration 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 Jira MCP Integration. 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 Jira MCP Integration MCP server (koveh/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 →