Delete a Jira ticket. This action is IRREVERSIBLE. If the ticket has subtasks, set deleteSubtasks to true or the deletion will fail.
AI agents call jira_delete_ticket 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.
This tool permanently deletes Jira tickets and cannot be undone. Deletion is explicitly marked as irreversible in the description. While the blast radius is limited by requiring explicit ticket identification, the irreversible destruction of project data, comments, and history represents a high-severity risk if an AI agent misuses this capability.
From the tool's definition Tool name is 'jira_delete_ticket' with description stating 'Delete a Jira ticket. This action is IRREVERSIBLE.' The explicit irreversible nature and permanent removal of data matches the Destructive category definition.
Attacks that exploit this kind of access
Delete a Jira ticket. This action is IRREVERSIBLE. If the ticket has subtasks, set deleteSubtasks to true or the deletion will fail. 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_delete_ticket: 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_delete_ticket 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_ticket 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_ticket. 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_ticket 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 →