delete_branch

Delete a branch 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-branch.md

WHAT IT DOES

What delete_branch does on Forgejo

AI agents call delete_branch 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 delete_branch is rated Critical

Deleting a branch is a destructive operation that cannot be undone. While not as critical as deleting an entire repository, it results in permanent loss of the branch reference and can impact development workflows.

From the tool's definition Tool name explicitly states 'delete_branch' and description states 'Delete a branch from a repository' — this is an irreversible deletion action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_branch 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 delete_branch, this is the rule to start with:

delete_branch Hidden

delete_branch 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": [
    "delete_branch"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_branch

What does the delete_branch tool do? +

Delete a branch 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_branch? +

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

delete_branch 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_branch? +

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

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

delete_branch 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

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →