git_worktree_unlock
A write tool on the GitHub MCP server.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/git-worktree-unlock.md
What git_worktree_unlock does on GitHub
AI agents use git_worktree_unlock to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
Why git_worktree_unlock is rated Medium
Unlocking a git worktree changes the state of the repository (removes a lock) and enables subsequent operations on that worktree. While the action itself is reversible (the worktree can be locked again), it modifies repository state rather than just reading it. This is less severe than Execute or Destructive since it doesn't run arbitrary code or delete data, but it does alter git state management.
From the tool's definition Tool named 'git_worktree_unlock' with description 'Git worktree unlock' - this modifies git worktree lock state, which changes repository state in a reversible manner.
Attacks that exploit this kind of access
The rule that runs git_worktree_unlock 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 git_worktree_unlock, this is the rule to start with:
git_worktree_unlock 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every git_worktree_unlock call is checked against it from then on.
Questions about git_worktree_unlock
git_worktree_unlock is a write tool on the GitHub MCP server. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP server in PolicyLayer and add a rule for git_worktree_unlock: 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.
git_worktree_unlock 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 git_worktree_unlock 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 git_worktree_unlock. 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.
git_worktree_unlock 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue