delete_issue

Delete a Jira issue

SERVERMcp Jira SOURCE1broseidon/mcp-jira-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/1broseidon-mcp-jira-server/delete-issue.md

WHAT IT DOES

What delete_issue does on Mcp Jira

AI agents call delete_issue to permanently remove resources in Mcp Jira, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_issue is rated Critical

Deleting a Jira issue is irreversible and removes project data that cannot be recovered through normal means. This qualifies as Destructive rather than Write. Severity is high because accidental deletion could disrupt project tracking and workflows, affecting multiple team members relying on issue history. Confidence is very high given the unambiguous language.

From the tool's definition Tool name is 'delete_issue' with description 'Delete a Jira issue'. The verb 'delete' explicitly indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_issue safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Jira, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_issue, this is the rule to start with:

delete_issue Hidden

delete_issue is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_issue"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Jira, apply this rule, and every delete_issue call is checked against it from then on.

FAQ

Questions about delete_issue

What does the delete_issue tool do? +

Delete a Jira issue. It is categorised as a Destructive tool in the Mcp Jira MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_issue? +

Register the Mcp Jira 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 Mcp Jira. Nothing to install.

What risk level is delete_issue? +

delete_issue is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_issue? +

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.

How do I block delete_issue completely? +

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.

What MCP server provides delete_issue? +

delete_issue is provided by the Mcp Jira MCP server (1broseidon/mcp-jira-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Jira, and thousands of servers like it.

This server

All 6 Mcp Jira tools → Critical-risk tools on this server →

Across the catalogue

delete_issue on Linear Kanban Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →