Delete a branch from a GitLab project
AI agents call delete_branches to permanently remove resources in GitLab MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a branch removes version control history and can cause loss of work if that branch contained unpushed commits or was the only reference to certain code. While git can recover deleted branches briefly through reflog, the primary effect is irreversible removal of a named reference. This is clearly destructive rather than merely Write (which would be reversible creation/modification).
From the tool's definition Tool name is 'delete_branches' and description states 'Delete a branch from a GitLab project'. The verb 'delete' combined with the irreversible nature of removing a git branch qualifies this as a destructive action.
Attacks that exploit this kind of access
Delete a branch from a GitLab project. It is categorised as a Destructive tool in the GitLab MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for delete_branches: 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 MCP Server. Nothing to install.
delete_branches 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 delete_branches 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 delete_branches. 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.
delete_branches is provided by the GitLab MCP Server MCP server (lucky-dersan/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →