add_merge_request_comment

THE RISK

Medium Risk

Why add_merge_request_comment needs a policy

Adding a comment creates new data on GitLab but is reversible (comments can be deleted/edited). While the tool description is empty, the tool name combined with the server's stated capability to 'add comments' provides sufficient evidence.

From the tool's definition Tool name 'add_merge_request_comment' indicates it creates/posts comments. Server description confirms the server 'add comments' to merge requests 'directly through the GitLab API.' This is a Write operation (creates data reversibly).

Documented attack patterns abuse exactly the kind of access add_merge_request_comment gives an agent:

POLICY

How to control add_merge_request_comment

PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP for Code Review, and nothing reaches the server without passing your rules. This is the rule we recommend for add_merge_request_comment:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_merge_request_comment": {
      "limits": [
        {
          "counter": "add_merge_request_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register GitLab MCP for Code Review — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitLab MCP for Code Review tools

Write approve_merge_request approve_merge_request Write unapprove_merge_request Unapprove a merge request. Read compare_versions compare_versions Read fetch_commit_diff fetch_commit_diff Read fetch_merge_request Fetch a GitLab merge request and its contents. Read fetch_merge_request_diff fetch_merge_request_diff Read get_project_merge_requests get_project_merge_requests

All 8 GitLab MCP for Code Review tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add_merge_request_comment

What does the add_merge_request_comment tool do? +

add_merge_request_comment. It is categorised as a Write tool in the GitLab MCP for Code Review 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 for Code Review 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 for Code Review. 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 for Code Review MCP server (mehmetakinn/gitlab-mcp-code-review). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitLab MCP for Code Review tool call.

Start from GitLab MCP for Code Review, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →