create_merge_request_discussion_note

Add a new discussion note to an existing merge request thread

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/create-merge-request-discussion-note.md

WHAT IT DOES

What create_merge_request_discussion_note does on Gitlab Mcp

AI agents use create_merge_request_discussion_note 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.

RISK

Why create_merge_request_discussion_note is rated Medium

This tool creates new discussion content (notes) on merge requests, which is a reversible write operation. It does not execute code, delete data, or affect financial systems. However, the medium severity reflects that malicious notes could add misleading information, spam, or false reviews to merge requests, potentially disrupting code review workflows and affecting project decisions.

From the tool's definition Tool explicitly performs 'Add a new discussion note' operation, which creates new data in an existing merge request thread without modifying or deleting existing content.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_merge_request_discussion_note safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_merge_request_discussion_note, this is the rule to start with:

create_merge_request_discussion_note Rate-limited

create_merge_request_discussion_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_discussion_note": {
      "limits": [
        {
          "counter": "create_merge_request_discussion_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every create_merge_request_discussion_note call is checked against it from then on.

FAQ

Questions about create_merge_request_discussion_note

What does the create_merge_request_discussion_note tool do? +

Add a new discussion note to an existing merge request thread. 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 create_merge_request_discussion_note? +

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

What risk level is create_merge_request_discussion_note? +

create_merge_request_discussion_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_discussion_note? +

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

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

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

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →