git_merge_to_base

Merge the current worktree branch back to the base branch. Only available in worktree isolation mode. Use when your work is complete and ready to be integrated.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/git-merge-to-base.md

WHAT IT DOES

What git_merge_to_base does on CoWork OS

AI agents invoke git_merge_to_base to trigger actions in CoWork OS. 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.

RISK

Why git_merge_to_base is rated High

A git merge operation triggers an external git operation that integrates changes from one branch into another. While not purely destructive (it can be undone with a revert), a merge can introduce conflicts, overwrite code, and alter the base branch state in ways that affect all collaborators.

From the tool's definition Merge the current worktree branch back to the base branch... Use when your work is complete and ready to be integrated.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_merge_to_base safely

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

git_merge_to_base Rate-limited

git_merge_to_base 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_merge_to_base": {
      "limits": [
        {
          "counter": "git_merge_to_base_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_merge_to_base

What does the git_merge_to_base tool do? +

Merge the current worktree branch back to the base branch. Only available in worktree isolation mode. Use when your work is complete and ready to be integrated. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_merge_to_base? +

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

What risk level is git_merge_to_base? +

git_merge_to_base is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit git_merge_to_base? +

Yes. Add a rate_limit block to the git_merge_to_base 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 git_merge_to_base completely? +

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

git_merge_to_base is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools → High-risk tools on this server →

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →