Delete stale merged branches from a repository.
AI agents call git_steer_branch_reap 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.
This tool performs irreversible deletion of Git branches. Although the branches are described as 'stale merged' (suggesting they are no longer active), deletion of repository branches cannot be undone without access to Git reflog or backups, and the action has permanent consequences for the repository state.
From the tool's definition The tool name explicitly contains 'reap' and the description states it will 'Delete stale merged branches from a repository.' The verb 'delete' is a destructive operation that irreversibly removes data (Git branches).
Attacks that exploit this kind of access
Delete stale merged branches from a repository. 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 git_steer_branch_reap: 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.
git_steer_branch_reap 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 git_steer_branch_reap 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 git_steer_branch_reap. 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.
git_steer_branch_reap 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 →