merge_method

Merge method (string, optional)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/merge-method.md

WHAT IT DOES

What merge_method does on GitHub

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

RISK

Why merge_method is rated Medium

This tool modifies repository state by setting merge method parameters (e.g., squash, rebase, merge commit), which affects how future PRs are merged. This is a reversible Write operation—the merge method can be changed later. It does not directly execute the merge (which would be Execute), nor does it delete data (Destructive).

From the tool's definition Tool name 'merge_method' in GitHub context refers to setting merge strategy for pull requests. The description 'Merge method (string, optional)' indicates configuration of how a PR merge will be executed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs merge_method safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For merge_method, this is the rule to start with:

merge_method Rate-limited

merge_method 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_method": {
      "limits": [
        {
          "counter": "merge_method_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every merge_method call is checked against it from then on.

FAQ

Questions about merge_method

What does the merge_method tool do? +

Merge method (string, optional). It is categorised as a Write tool in the GitHub 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_method? +

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

What risk level is merge_method? +

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

Can I rate-limit merge_method? +

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

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

merge_method is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →