delete_label

THE RISK

Critical Risk

Why delete_label needs a policy

This tool permanently removes a label from a repository, which is an irreversible destructive action. Once deleted, any label references may be lost or orphaned across issues and pull requests. While not as critical as deleting entire repositories or user accounts, it is a destructive operation that cannot be undone.

From the tool's definition Tool name is 'delete_label' with description 'Delete a label from a repository'. The word 'delete' combined with 'label' indicates irreversible removal of data.

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

POLICY

How to control delete_label

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

policy.json

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

delete_label 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 Forgejo — 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 Forgejo tools

Destructive admin_delete_user Delete a user (requires admin privileges) Destructive delete_branch Delete a branch from a repository Destructive delete_file Delete a file from a repository Destructive delete_issue_comment Delete a comment on an issue Destructive delete_milestone Delete a milestone from a repository Destructive delete_org Delete an organization Destructive delete_repo Delete a repository by owner and name Destructive remove_team_member Remove a member from a team

All 103 Forgejo 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 Forgejo → 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_label

What does the delete_label tool do? +

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

Register the Forgejo MCP server in PolicyLayer and add a rule for delete_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 Forgejo. Nothing to install.

What risk level is delete_label? +

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

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

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

delete_label is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Forgejo tool call.

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

CHECK YOUR STACK →