Delete an issue from a GitHub repository using GraphQL API
AI agents call delete_issue to permanently remove resources in GitHub MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an issue from a repository, which is an irreversible operation. Even though issues can technically be restored by repository admins in some cases, the primary function is destructive removal of data. The Destructive category takes precedence over Write (which covers reversible modifications) because deletion cannot be undone by standard operations.
From the tool's definition Tool name is 'delete_issue' and description explicitly states 'Delete an issue from a GitHub repository'. Deletion is irreversible; the issue cannot be recovered.
Attacks that exploit this kind of access
Delete an issue from a GitHub repository using GraphQL API. It is categorised as a Destructive tool in the GitHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub 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 GitHub 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 GitHub MCP Server MCP server (tuanle96/mcp-github). 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 →