git_worktree_remove
A destructive tool on the GitHub MCP server.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/git-worktree-remove.md
What git_worktree_remove does on GitHub
AI agents call git_worktree_remove to permanently remove resources in GitHub, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why git_worktree_remove is rated Critical
Removing a git worktree is a destructive operation that eliminates a working tree associated with a repository. While the repository itself may persist, the worktree deletion cannot be reversed through normal git operations and represents an irreversible state change. This qualifies as Destructive rather than Execute because the operation is inherently destructive in nature.
From the tool's definition Tool name 'git_worktree_remove' and description 'Git worktree remove' indicates removal/deletion of git worktree data structures, which cannot be undone without recovery operations.
Attacks that exploit this kind of access
The rule that runs git_worktree_remove safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_worktree_remove, this is the rule to start with:
git_worktree_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every git_worktree_remove call is checked against it from then on.
Questions about git_worktree_remove
git_worktree_remove is a destructive tool on the GitHub MCP server. It is categorised as a Destructive tool in the GitHub MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub MCP server in PolicyLayer and add a rule for git_worktree_remove: 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 GitHub. Nothing to install.
git_worktree_remove 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_worktree_remove 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_worktree_remove. 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_worktree_remove is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
Across the catalogue