merge_branch_summary · GitBranch MCP: Risk & Policy

WHAT IT DOES

What merge_branch_summary does on GitBranchMCP

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

WHY IT NEEDS A POLICY

Why merge_branch_summary needs a policy

This tool modifies branch content by merging summaries, which is a reversible write operation. It does not irreversibly delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial).

From the tool's definition Tool name 'merge_branch_summary' and description indicate merging content from a source branch to a target branch.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_branch_summary Rate-limited

merge_branch_summary 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": {
    "merge_branch_summary": {
      "limits": [
        {
          "counter": "merge_branch_summary_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 GitBranchMCP, so you can run agents against it safely.

FAQ

Questions about merge_branch_summary

What does the merge_branch_summary tool do? +

将来源分支以 summary merge 方式合并到目标分支。. It is categorised as a Write tool in the GitBranchMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on merge_branch_summary? +

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

What risk level is merge_branch_summary? +

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

Can I rate-limit merge_branch_summary? +

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

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

merge_branch_summary is provided by the GitBranch MCP server (lianggaoyuan/gitbranchmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.