Generate ready-to-run git worktree commands so each active agent gets its own
AI agents invoke suggest_worktrees to trigger actions in Claude Team MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool produces executable git commands as output. While git worktree itself is not destructive (changes are isolated and reversible), executing arbitrary git commands falls under Execute category.
From the tool's definition Tool generates and provides 'ready-to-run git worktree commands' — these are shell commands intended for execution. git worktree creates isolated working directories that modify the local repository state.
Attacks that exploit this kind of access
Generate ready-to-run git worktree commands so each active agent gets its own. It is categorised as a Execute tool in the Claude Team MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Team MCP server in PolicyLayer and add a rule for suggest_worktrees: 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 Claude Team MCP. Nothing to install.
suggest_worktrees is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the suggest_worktrees 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 suggest_worktrees. 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.
suggest_worktrees is provided by the Claude Team MCP server (lakshan12367/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 →