New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_label

Delete a label from a repository

SERVERForgejo SOURCEsqcows/forgejo-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/delete-label.md

What delete_label does on Forgejo

AI agents call delete_label to permanently remove resources in Forgejo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_label is rated Critical

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.

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.

More on Forgejo, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Forgejo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.