merge_summary_to_main · GitBranch MCP: Risk & Policy

WHAT IT DOES

What merge_summary_to_main does on GitBranchMCP

AI agents use merge_summary_to_main 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_summary_to_main needs a policy

This tool creates or modifies mainline data by merging branch summaries, making it a Write operation. It's reversible (a merge can be undone or reverted in most systems), so it does not rise to Destructive. Severity is medium because misuse could corrupt decision logs or mainline content, but the blast radius is limited to a local documentation system rather than production systems or financial data.

From the tool's definition Tool name 'merge_summary_to_main' and description indicating merging branch conclusions to mainline. The description translates to 'Call when user requests merging a branch conclusion to the mainline.' This performs a write/modification operation on the…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_summary_to_main Rate-limited

merge_summary_to_main 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_summary_to_main": {
      "limits": [
        {
          "counter": "merge_summary_to_main_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_summary_to_main

What does the merge_summary_to_main tool do? +

当用户要求把某个分支结论合并到主线时调用。. 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_summary_to_main? +

Register the GitBranch MCP server in PolicyLayer and add a rule for merge_summary_to_main: 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_summary_to_main? +

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

Can I rate-limit merge_summary_to_main? +

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

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

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