create_merge_request · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_merge_request does on Mcp Gitlab

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

WHY IT NEEDS A POLICY

Why create_merge_request needs a policy

Creating a merge request is a write operation that adds new data to the repository but is fully reversible—merge requests can be closed, deleted, or abandoned without permanent data loss. This distinguishes it from destructive actions. While it could trigger CI/CD pipelines or workflows depending on configuration, the direct action itself is creating/modifying metadata.

From the tool's definition Tool creates a new merge request, which modifies repository state by adding a new merge request object. Description explicitly states 'dry_run=true by default', indicating the tool supports safe exploration but the actual operation is reversible (merge…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_merge_request Rate-limited

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

FAQ

Questions about create_merge_request

What does the create_merge_request tool do? +

Create a new merge request. dry_run=true by default. It is categorised as a Write tool in the Mcp Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_merge_request? +

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

What risk level is create_merge_request? +

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

Can I rate-limit create_merge_request? +

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

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

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