AI agents call worktree_status to retrieve information from Lockstep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
worktree_status purely retrieves and displays information about a worktree's state (commits, file changes). It performs no side effects, data modification, code execution, or resource destruction. This is a straightforward read/query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate status retrieval: 'Get the status of a worktree' with read-only queries about commits, modified files, and untracked files. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Get the status of a worktree including commits ahead/behind main, modified files, and untracked files. Use this to check an implementer. It is categorised as a Read tool in the Lockstep MCP Server, which means it retrieves data without modifying state.
Register the Lockstep MCP server in PolicyLayer and add a rule for worktree_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 Lockstep. Nothing to install.
worktree_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 worktree_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 worktree_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.
worktree_status is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). 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 →