comment_merge_request · GitLab MCP: Risk & Policy

WHAT IT DOES

What comment_merge_request does on GitLab MCP

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

WHY IT NEEDS A POLICY

Why comment_merge_request needs a policy

Commenting on a merge request modifies the MR's discussion thread by adding content, but this is reversible (comments can be edited or deleted). It does not execute code, delete data, or move money. The severity is medium rather than low because in a multi-tenant GitLab environment, an agent could spam comments, inject misleading information into code reviews, or disrupt collaboration workflows.

From the tool's definition Tool creates a new comment/note on a merge request, which is a non-destructive modification to project data. The description explicitly states 'Add a comment (note)' - a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

comment_merge_request Rate-limited

comment_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": {
    "comment_merge_request": {
      "limits": [
        {
          "counter": "comment_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 GitLab MCP, so you can run agents against it safely.

FAQ

Questions about comment_merge_request

What does the comment_merge_request tool do? +

Add a comment (note) to a merge request. It is categorised as a Write tool in the GitLab MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on comment_merge_request? +

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

What risk level is comment_merge_request? +

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

Can I rate-limit comment_merge_request? +

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

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

comment_merge_request is provided by the GitLab MCP server (shahabmosavi/gitlab_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.