Clean up orphaned worktree entries
AI agents use treehouse_prune to create or update resources in Treehouse Worktree — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Treehouse Worktree environment.
This tool modifies the git worktree metadata by removing orphaned entries, which is a reversible operation (entries could theoretically be recreated or recovered from git state). This is Write rather than Destructive because it targets metadata/state entries rather than core repository data or user work.
From the tool's definition Tool performs cleanup of 'orphaned worktree entries,' which modifies the state of the worktree management system by removing obsolete entries. The description indicates it 'cleans up' entries rather than querying or deleting actual code/branches.
Attacks that exploit this kind of access
Clean up orphaned worktree entries. It is categorised as a Write tool in the Treehouse Worktree MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Treehouse Worktree MCP server in PolicyLayer and add a rule for treehouse_prune: 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 Treehouse Worktree. Nothing to install.
treehouse_prune is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the treehouse_prune 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 treehouse_prune. 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.
treehouse_prune is provided by the Treehouse Worktree MCP server (mark-hingston/treehouse-worktree). 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 →