clear_issue_labels

Remove all labels from an issue

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/clear-issue-labels.md

WHAT IT DOES

What clear_issue_labels does on Forgejo

AI agents call clear_issue_labels 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.

RISK

Why clear_issue_labels is rated Critical

Removes all labels irreversibly from an issue, requiring manual re-addition to restore.

From the tool's definition Remove all labels from an issue

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_issue_labels safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_issue_labels, this is the rule to start with:

clear_issue_labels Hidden

clear_issue_labels is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every clear_issue_labels call is checked against it from then on.

FAQ

Questions about clear_issue_labels

What does the clear_issue_labels tool do? +

Remove all labels from an issue. 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 clear_issue_labels? +

Register the Forgejo MCP server in PolicyLayer and add a rule for clear_issue_labels: 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 clear_issue_labels? +

clear_issue_labels 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 clear_issue_labels? +

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

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

clear_issue_labels 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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools → Critical-risk tools on this server →

Across the catalogue

clear_project_index on ACE-MCP →clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →