Lists, adds, removes, locks, unlocks, or prunes git worktrees for managing multiple working trees. Returns structured data with worktree paths, branches, and HEAD commits.
AI agents call worktree to permanently remove resources in Lint — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool can remove and prune git worktrees, which are irreversible destructive operations that delete working tree data. It also performs write/execute operations like adding and locking worktrees. Following the most-severe-applicable rule, the destructive 'remove' and 'prune' capabilities dominate the classification. Severity is high because misuse could cause loss of uncommitted work across multiple working trees.
From the tool's definition removes, locks, unlocks, or prunes git worktrees
Documented attack patterns abuse exactly the kind of access worktree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lint, and nothing reaches the server without passing your rules. This is the rule we recommend for worktree:
{
"version": "1",
"default": "deny",
"hide": [
"worktree"
]
} worktree disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Lists, adds, removes, locks, unlocks, or prunes git worktrees for managing multiple working trees. Returns structured data with worktree paths, branches, and HEAD commits. It is categorised as a Destructive tool in the Lint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lint MCP server in PolicyLayer and add a rule for worktree: 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 Lint. Nothing to install.
worktree 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 worktree 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 worktree. 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.
worktree is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Lint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.