delete_issue_comment

THE RISK

Critical Risk

Why delete_issue_comment needs a policy

Deleting a comment removes data permanently and cannot be undone (no restore mechanism typical in GitHub). This qualifies as Destructive rather than Write. Severity is high because bulk misuse could erase important discussion/audit trails, though impact is scoped to a single repository. Confidence is high because the intent is explicit in the name and description.

From the tool's definition Tool name is 'delete_issue_comment' and description states 'Delete an issue comment' — this is an irreversible deletion operation.

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

POLICY

How to control delete_issue_comment

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Repos Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_issue_comment:

policy.json

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

delete_issue_comment 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 GitHub Repos Manager 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 GitHub Repos Manager MCP Server tools

Destructive delete_deploy_key Remove deploy keys. Destructive delete_file Delete a file from a repository. Destructive delete_label Delete a label from a repository Destructive delete_milestone Delete a milestone Destructive delete_webhook Remove webhooks. Execute cancel_workflow_run Cancel running workflows. Execute trigger_workflow Manually trigger workflow dispatches (handle input parameters). Write remove_assignees_from_issue Remove assignees from an issue

All 84 GitHub Repos Manager 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 GitHub Repos Manager 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_issue_comment

What does the delete_issue_comment tool do? +

Delete an issue comment. It is categorised as a Destructive tool in the GitHub Repos Manager 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_issue_comment? +

Register the GitHub Repos Manager MCP Server MCP server in PolicyLayer and add a rule for delete_issue_comment: 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 Repos Manager MCP Server. Nothing to install.

What risk level is delete_issue_comment? +

delete_issue_comment 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_comment? +

Yes. Add a rate_limit block to the delete_issue_comment 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_comment completely? +

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

delete_issue_comment is provided by the GitHub Repos Manager MCP Server MCP server (kurdin/github-repos-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub Repos Manager MCP Server tool call.

Start from GitHub Repos Manager 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 →