create_merge_request_tool · MCP Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_merge_request_tool does on MCP Gitlab

AI agents use create_merge_request_tool 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_tool needs a policy

Creating a merge request is a write operation that modifies repository state by proposing code changes, but is fully reversible (can be closed/rejected). It does not execute arbitrary code, delete data irreversibly, or move funds.

From the tool's definition Tool name 'create_merge_request_tool' indicates creation of a merge request, a reversible code change proposal in Git workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_merge_request_tool Rate-limited

create_merge_request_tool 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_tool": {
      "limits": [
        {
          "counter": "create_merge_request_tool_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_tool

What does the create_merge_request_tool tool do? +

create_merge_request_tool. 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_tool? +

Register the MCP Gitlab MCP server in PolicyLayer and add a rule for create_merge_request_tool: 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_tool? +

create_merge_request_tool 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_tool? +

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

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

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