Permanently delete an issue and all its comments. e.g., id:
AI agents call delete_issue to permanently remove resources in Issue Tracker MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (issues and associated comments) that cannot be undone, fitting the Destructive category. The severity is high because deletion of project management artifacts can disrupt team workflows, audit trails, and historical records, though it is scoped to individual issues rather than bulk/systemic destruction. Confidence is high due to explicit language confirming permanent deletion.
From the tool's definition Tool name is 'delete_issue' with description stating 'Permanently delete an issue and all its comments.' The word 'Permanently' and 'delete' clearly indicate irreversible data destruction.
Attacks that exploit this kind of access
Permanently delete an issue and all its comments. e.g., id:. It is categorised as a Destructive tool in the Issue Tracker MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Issue Tracker 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 Issue Tracker MCP. 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 Issue Tracker MCP server (josephtandle/jira-mcp-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 →