Delete a repository branch permanently. Requires branch. Recommended pre-check: gitlab_get_branch.
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.
The tool permanently deletes a repository branch, which cannot be undone. While repository branches can sometimes be recovered through Git history or backups in certain scenarios, the primary effect is irreversible data removal from the repository's active branch structure. The high severity reflects that deleting a branch can disrupt team workflows, remove work-in-progress code, and affect CI/CD pipelines.
From the tool's definition Tool performs permanent deletion ('Delete a repository branch permanently'). This is an irreversible operation matching the Destructive category definition.
Documented attack patterns abuse exactly the kind of access gitlab_delete_branch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_delete_branch:
{
"version": "1",
"default": "deny",
"hide": [
"gitlab_delete_branch"
]
}gitlab_delete_branch disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a repository branch permanently. Requires branch. Recommended pre-check: gitlab_get_branch. 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.
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.
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.
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.
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.
gitlab_delete_branch is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.