create_merge_request_note · GitLab MCP Server MCP

WHAT IT DOES

What create_merge_request_note does on GitLab MCP Server

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

This tool creates new data (a comment/note) on a merge request, which is a reversible operation. It does not execute code, delete data, or move money. The write operation is scoped to MR discussion artifacts. Severity is medium because malicious comments could spam, defame, or mislead reviewers, but the impact is limited to the MR discussion context and can be deleted by administrators.

From the tool's definition Tool name 'create_merge_request_note' and description '新增 Merge Request 留言' (Add Merge Request comment) indicate creation of a new comment/note on a merge request.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_merge_request_note Rate-limited

create_merge_request_note 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_note": {
      "limits": [
        {
          "counter": "create_merge_request_note_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 create_merge_request_note

What does the create_merge_request_note tool do? +

新增 Merge Request 留言. 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 create_merge_request_note? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for create_merge_request_note: 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 create_merge_request_note? +

create_merge_request_note 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_note? +

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

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

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