comment_on_merge_request · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What comment_on_merge_request does on Qodev Gitlab

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

WHY IT NEEDS A POLICY

Why comment_on_merge_request needs a policy

Commenting on a merge request creates new data in the GitLab system, making it a Write operation. The severity is low because comments are reversible (can be edited/deleted), have limited blast radius, and do not affect code integration, pipeline execution, or repository state directly.

From the tool's definition Tool name is 'comment_on_merge_request' which indicates creating comments (write operation). No description provided, but context from sibling tools (comment_on_issue, create_inline_comment) confirms this is a commenting tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

comment_on_merge_request Rate-limited

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

FAQ

Questions about comment_on_merge_request

What does the comment_on_merge_request tool do? +

comment_on_merge_request. It is categorised as a Write tool in the Qodev 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 comment_on_merge_request? +

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

What risk level is comment_on_merge_request? +

comment_on_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_on_merge_request? +

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

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

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