add_merge_request_comment · GitLab MCP Server MCP

WHAT IT DOES

What add_merge_request_comment does on GitLab MCP Server

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

WHY IT NEEDS A POLICY

Why add_merge_request_comment needs a policy

Adding a comment creates new data in GitLab and modifies the merge request's comment thread. This is reversible (comments can be deleted) and has no destructive effects. It does not execute arbitrary code or trigger financial transactions.

From the tool's definition Tool name 'add_merge_request_comment' and description 'Add a comment to a merge request' indicate creation of new comment data. This is a write operation that modifies merge request state by appending new content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_merge_request_comment Rate-limited

add_merge_request_comment 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": {
    "add_merge_request_comment": {
      "limits": [
        {
          "counter": "add_merge_request_comment_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 Server, so you can run agents against it safely.

FAQ

Questions about add_merge_request_comment

What does the add_merge_request_comment tool do? +

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

How do I enforce a policy on add_merge_request_comment? +

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

What risk level is add_merge_request_comment? +

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

Can I rate-limit add_merge_request_comment? +

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

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

add_merge_request_comment is provided by the GitLab MCP Server MCP server (therealchristhomas/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

add_merge_request_comment is one line of GitLab MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →