git-merge · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git-merge does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why git-merge needs a policy

git-merge modifies the repository by combining branches, creating merge commits and updating the working directory. Unlike destructive operations (which cannot be undone), merges can be reverted with git-revert or git-reset. The 'conflict detection' mention confirms it handles merge logic safely. This is a classic Write operation: creates or modifies data reversibly.

From the tool's definition Tool name 'git-merge' and description 'Merge a branch into the current branch' indicate a reversible modification of repository state (commit history, working directory).

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 GitHub 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 with conflict detection. It is categorised as a Write tool in the GitHub 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 GitHub 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 GitHub 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 GitHub MCP Server MCP server (jungchihoon/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.