AI agents call delete_issue 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.
Deleting a Jira issue irreversibly removes project tracking data, issue history, and linked artifacts. This action cannot be undone and has significant blast radius in a team environment where issues are central to project management, communication, and audit trails. The caution warning reinforces the destructive nature. This is the most severe category among applicable ones (Destructive > Execute > Write > Read).
From the tool's definition Tool name 'delete_issue' and description states 'Delete a Jira issue (use with caution)' - the caution warning itself indicates irreversible data loss.
Documented attack patterns abuse exactly the kind of access delete_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_issue:
{
"version": "1",
"default": "deny",
"hide": [
"delete_issue"
]
}delete_issue disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a Jira issue (use with caution). 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 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 Server. Nothing to install.
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 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 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.
delete_issue is provided by the Jira MCP Server MCP server (redhat-community-ai-tools/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.