merge_pull_request · Mcp Gmail MCP: Risk & Policy

WHAT IT DOES

What merge_pull_request does on Mcp Gmail

AI agents invoke merge_pull_request to trigger actions in Mcp Gmail. 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.

WHY IT NEEDS A POLICY

Why merge_pull_request needs a policy

Merging a pull request is an irreversible integration of code changes into a target branch. While a revert commit can undo the logical change, the merge commit itself remains in history. This constitutes a significant Execute action (triggering external operations and modifying repo state), bordering on Destructive.

From the tool's definition 'Merge a pull request' — merging combines branches and triggers CI/CD pipelines, modifies repository history, and cannot be easily undone without force-push or revert commits

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_pull_request Rate-limited

merge_pull_request 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": {
    "merge_pull_request": {
      "limits": [
        {
          "counter": "merge_pull_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about merge_pull_request

What does the merge_pull_request tool do? +

Merge a pull request. It is categorised as a Execute tool in the Mcp Gmail MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on merge_pull_request? +

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

What risk level is merge_pull_request? +

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

Can I rate-limit merge_pull_request? +

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

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

merge_pull_request is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.