[git-fabric] Delete a branch.
AI agents call fabric_git_delete_branch to permanently remove resources in Git Steer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Branch deletion is irreversible in normal git workflows. While technically recoverable via reflog in some cases, it constitutes a destructive action that permanently removes code history and references. In the context of an autonomous GitHub management engine, unauthorized or erroneous branch deletion poses significant risk to repository integrity, CI/CD pipelines, and development workflows.
From the tool's definition 'Delete a branch' - irreversibly removes a git branch and any unmerged commits on that branch, a destructive operation that cannot be undone without access to git reflog or backups.
Attacks that exploit this kind of access
[git-fabric] Delete a branch. It is categorised as a Destructive tool in the Git Steer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git Steer MCP server in PolicyLayer and add a rule for fabric_git_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 Git Steer. Nothing to install.
fabric_git_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 fabric_git_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 fabric_git_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.
fabric_git_delete_branch is provided by the Git Steer MCP server (ry-ops/git-steer). 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 →