Delete a branch from a GitLab repository.
AI agents call delete_branch_tool to permanently remove resources in MCP Gitlab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a branch removes code history and references irreversibly. While the data itself may exist in Git history, the branch pointer is destroyed and dependent workflows (CI/CD pipelines, pull requests, integrations) may break. This is irreversible at the application level and represents a destructive operation that exceeds the scope of reversible writes.
From the tool's definition The tool description explicitly states 'Delete a branch from a GitLab repository.' The verb 'delete' combined with modifying a repository's branch structure indicates an irreversible action.
Attacks that exploit this kind of access
Delete a branch from a GitLab repository. It is categorised as a Destructive tool in the MCP Gitlab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Gitlab MCP server in PolicyLayer and add a rule for delete_branch_tool: 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 MCP Gitlab. Nothing to install.
delete_branch_tool 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_branch_tool 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_branch_tool. 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_branch_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). 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 →