delete_ticket

THE RISK

Critical Risk

Why delete_ticket needs a policy

Deletion of tickets is an irreversible operation that removes data permanently from Jira. This constitutes a destructive action with potentially significant blast radius if invoked by an AI agent on the wrong ticket(s), causing loss of issue tracking data, audit trails, and team context. Severity is high rather than critical because impact is typically scoped to individual tickets rather than systemic infrastructure.

From the tool's definition Tool name 'delete_ticket' and description explicitly states it deletes a ticket via Jira's DELETE endpoint /rest/api/3/issue/{issueIdOrKey}. The action is irreversible.

Documented attack patterns abuse exactly the kind of access delete_ticket gives an agent:

POLICY

How to control delete_ticket

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_ticket:

policy.json

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

delete_ticket disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Jira MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Server tools

Execute execute_jql Execute a JQL query on Jira on the api /rest/api/3/search/jql. Do not use markdown in your Write add_attachment_from_confluence Add an attachment to a ticket on Jira from a Confluence page by its name on the api /rest/ Write add_attachment_from_public_url Add an attachment from a public url to a ticket on Jira on the api /rest/api/3/issue/{issu Write assign_ticket Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use m Write create_ticket Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field. Write edit_ticket Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in Read get_all_statuses Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your quer Read get_only_ticket_name_and_description Get the name and description of the requested tickets on the api /rest/api/3/search/jql. D

All 11 Jira MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Jira MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_ticket

What does the delete_ticket tool do? +

Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query. 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.

How do I enforce a policy on delete_ticket? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for 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.

What risk level is delete_ticket? +

delete_ticket 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_ticket? +

Yes. Add a rate_limit block to the 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.

How do I block delete_ticket completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides delete_ticket? +

delete_ticket is provided by the Jira MCP Server MCP server (ks-gen-ai/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jira MCP Server tool call.

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.

CHECK YOUR STACK →