Critical Risk →

delete_issue_label

Remove a label from an issue in a repository

How to control delete_issue_label ↓

What delete_issue_label does on AtomGit MCP Server

AI agents call delete_issue_label to permanently remove resources in AtomGit MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_issue_label needs a policy

This tool removes a label from an issue, which is a destructive action as it irreversibly deletes the label association. While the blast radius is limited (only affects label associations on issues, not the issues themselves), the action cannot be undone without manually re-adding the label.

From the tool's definition 'delete_issue_label' and 'Remove a label from an issue in a repository'

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

How to control delete_issue_label

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_issue_label"
  ]
}

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

  1. Create a free account and register AtomGit MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_issue_label

What does the delete_issue_label tool do? +

Remove a label from an issue in a repository. It is categorised as a Destructive tool in the AtomGit 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_label? +

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

What risk level is delete_issue_label? +

delete_issue_label 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_label? +

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

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

delete_issue_label is provided by the AtomGit MCP Server MCP server (kaiyuanxiaobing/atomgit-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 AtomGit MCP Server tool call.

Start from AtomGit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

22 AtomGit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.