git_branch_delete

Delete a branch. Removes the specified branch from the repository. By default, only fully merged branches can be deleted unless force is set to true.

Server Git MCP Server wty0512/git-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What git_branch_delete does on Git MCP Server

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

Why git_branch_delete needs a policy

This tool irreversibly deletes git branches, which cannot be undone without access to reflog or backups. While the impact is scoped to branch metadata rather than file data, branch deletion is a destructive operation that destroys version control history pointers. The force flag allowing deletion of unmerged branches increases risk.

From the tool's definition Tool name is 'git_branch_delete' and description states it 'Delete a branch. Removes the specified branch from the repository.' The word 'Delete' and 'Removes' indicate irreversible deletion of a git branch.

Questions about git_branch_delete

What does the git_branch_delete tool do? +

Delete a branch. Removes the specified branch from the repository. By default, only fully merged branches can be deleted unless force is set to true. It is categorised as a Destructive tool in the Git 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 git_branch_delete? +

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

What risk level is git_branch_delete? +

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

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

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

git_branch_delete is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.