Get detailed status of a specific worktree or all worktrees
AI agents call treehouse_status to retrieve information from Treehouse Worktree without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports the current state of git worktrees. It performs no modifications, deletions, or external operations—purely informational. The verb 'Get' and the focus on status reporting are characteristic of Read operations. Severity is low because status queries have minimal blast radius even if misused by an agent.
From the tool's definition Tool name 'treehouse_status' and description 'Get detailed status of a specific worktree or all worktrees' indicate a query operation that retrieves information without modification.
Attacks that exploit this kind of access
Get detailed status of a specific worktree or all worktrees. It is categorised as a Read tool in the Treehouse Worktree MCP Server, which means it retrieves data without modifying state.
Register the Treehouse Worktree MCP server in PolicyLayer and add a rule for treehouse_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the treehouse_status 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_status. 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_status 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 →