git_merge · Git MCP Server MCP: Risk & Policy

WHAT IT DOES

What git_merge does on Git MCP Server

AI agents use git_merge to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.

WHY IT NEEDS A POLICY

Why git_merge needs a policy

git_merge integrates changes from one branch into another, which is a write operation that modifies the repository's commit history and working state. It is reversible (via git reset or revert), so it does not qualify as Destructive. However, misuse can introduce unwanted code, break builds, or corrupt branch history at scale, warranting a high severity rating.

From the tool's definition Merge a branch into the current branch. Combines changes from the specified branch into the current branch with configurable merge strategies.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_merge Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_merge": {
      "limits": [
        {
          "counter": "git_merge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Git MCP Server, so you can run agents against it safely.

FAQ

Questions about git_merge

What does the git_merge tool do? +

Merge a branch into the current branch. Combines changes from the specified branch into the current branch with configurable merge strategies. It is categorised as a Write tool in the Git MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_merge? +

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

What risk level is git_merge? +

git_merge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git_merge? +

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

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

git_merge is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.