gitlab_delete_branch

Delete a branch. Refuses to delete protected branches.

SERVERGitlab SOURCEdkeeno/gitlab-mcp-server

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/dkeeno-gitlab-mcp-server/gitlab-delete-branch.md

WHAT IT DOES

What gitlab_delete_branch does on Gitlab

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

RISK

Why gitlab_delete_branch is rated Critical

Deleting a branch is a destructive action that irreversibly removes code and commit history. Although the tool includes a safeguard (refusing protected branches), the core capability is destructive. The blast radius is high: an agent could delete active development branches, causing loss of work and disruption to team workflows.

From the tool's definition Tool name 'gitlab_delete_branch' and description states it 'Delete[s] a branch' — an irreversible operation that removes version control history and data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitlab_delete_branch safely

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

gitlab_delete_branch Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gitlab_delete_branch

What does the gitlab_delete_branch tool do? +

Delete a branch. Refuses to delete protected branches. It is categorised as a Destructive tool in the Gitlab 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 gitlab_delete_branch? +

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

What risk level is gitlab_delete_branch? +

gitlab_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 gitlab_delete_branch? +

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

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

gitlab_delete_branch is provided by the Gitlab MCP server (dkeeno/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 56 Gitlab 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 code and CI agents →Blast radius →Tool call approval →