detach
Create a detached HEAD worktree (optional, default: false) (boolean, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/detach.md
What detach does on GitHub
AI agents invoke detach to trigger actions in GitHub. 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.
Why detach is rated High
The tool creates a detached HEAD worktree, which is a git operation. However, the description is very minimal and appears to describe a parameter rather than a full tool, lowering confidence. Creating a detached HEAD is an Execute-level operation as it triggers a git operation that affects the working tree state.
From the tool's definition 'Create a detached HEAD worktree' - this creates a git worktree in detached HEAD state, which is a git operation that modifies repository state
Attacks that exploit this kind of access
The rule that runs detach 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 detach, this is the rule to start with:
detach stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 detach call is checked against it from then on.
Questions about detach
Create a detached HEAD worktree (optional, default: false) (boolean, optional). It is categorised as a Execute tool in the GitHub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GitHub MCP server in PolicyLayer and add a rule for detach: 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.
detach 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 detach 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 detach. 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.
detach 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.
Across the catalogue