merge_merge_request · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What merge_merge_request does on Qodev Gitlab

AI agents invoke merge_merge_request to trigger actions in Qodev Gitlab. 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_merge_request needs a policy

Merging a merge request is an execution-level operation that combines branches, potentially modifying the main/protected branch of a repository. While it is technically reversible via a revert, the act of merging triggers external operations (CI/CD pipelines, branch updates, deployment hooks) and permanently alters the commit history in a meaningful way.

From the tool's definition Tool name 'merge_merge_request' implies triggering a merge operation in GitLab, which executes a git merge and modifies repository state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_merge_request Rate-limited

merge_merge_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_merge_request": {
      "limits": [
        {
          "counter": "merge_merge_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 Qodev Gitlab, so you can run agents against it safely.

FAQ

Questions about merge_merge_request

What does the merge_merge_request tool do? +

merge_merge_request. It is categorised as a Execute tool in the Qodev Gitlab 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_merge_request? +

Register the Qodev Gitlab MCP server in PolicyLayer and add a rule for merge_merge_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 Qodev Gitlab. Nothing to install.

What risk level is merge_merge_request? +

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

Can I rate-limit merge_merge_request? +

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

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

merge_merge_request is provided by the Qodev Gitlab MCP server (qodevai/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.