Create a new git worktree for parallel development
AI agents use worktree_create to create or update resources in Climux — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Climux environment.
Creating a git worktree modifies repository structure and creates new working directories with their own branch checkouts. While reversible (worktrees can be deleted), this is a write operation that changes repository state. Severity is high because an AI agent could create numerous worktrees consuming disk space or creating confusing branch states that disrupt development workflows.
From the tool's definition Tool description states 'Create a new git worktree for parallel development' — the verb 'Create' indicates data modification. Git worktrees are persistent filesystem structures that modify the repository state.
Documented attack patterns abuse exactly the kind of access worktree_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Climux, and nothing reaches the server without passing your rules. This is the rule we recommend for worktree_create:
{
"version": "1",
"default": "deny",
"tools": {
"worktree_create": {
"limits": [
{
"counter": "worktree_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}worktree_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new git worktree for parallel development. It is categorised as a Write tool in the Climux MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Climux MCP server in PolicyLayer and add a rule for worktree_create: 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 Climux. Nothing to install.
worktree_create 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 worktree_create 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_create. 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_create is provided by the Climux MCP server (veithly/climux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Climux, 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.
9 Climux tools catalogued and risk-classified — across an index of 43,000+ MCP servers.