worktree

Path to the worktree directory to unlock (string, required)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/worktree.md

WHAT IT DOES

What worktree does on GitHub

AI agents call worktree as a supporting operation in GitHub workflows.

RISK

Why worktree is rated Low

The description is uninformative and appears to be a parameter definition rather than a tool description. 'Unlock' a worktree is a git operation that removes a lock on a worktree, which is a Write/Execute-level operation, but without sufficient context to determine the full scope, confidence is low. Git worktree unlock is generally a reversible, low-impact operation.

From the tool's definition Tool description only says 'Path to the worktree directory to unlock (string, required)' — this appears to be a parameter description, not a full tool description.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs worktree safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For worktree, this is the rule to start with:

worktree Rate-limited

worktree gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "worktree": {
      "limits": [
        {
          "counter": "worktree_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every worktree call is checked against it from then on.

FAQ

Questions about worktree

What does the worktree tool do? +

Path to the worktree directory to unlock (string, required). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on worktree? +

Register the GitHub MCP server in PolicyLayer and add a rule for worktree: 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 GitHub. Nothing to install.

What risk level is worktree? +

worktree is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit worktree? +

Yes. Add a rate_limit block to the worktree 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.

How do I block worktree completely? +

Set action: deny in the PolicyLayer policy for worktree. 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.

What MCP server provides worktree? +

worktree is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →