gitlab_add_mr_note

Add a note (comment) to a merge request

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/gitlab-add-mr-note.md

WHAT IT DOES

What gitlab_add_mr_note does on Sage MCP

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

RISK

Why gitlab_add_mr_note is rated Medium

Adding a note/comment to a merge request creates new data in the GitLab system. This is a Write category operation because: (1) it creates new content (a comment), (2) the action is reversible (comments can be edited or deleted), and (3) it does not execute code, delete data irreversibly, or move money.

From the tool's definition Tool name 'gitlab_add_mr_note' and description 'Add a note (comment) to a merge request' indicate creation of new comment data on a merge request, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitlab_add_mr_note safely

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

gitlab_add_mr_note Rate-limited

gitlab_add_mr_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": {
    "gitlab_add_mr_note": {
      "limits": [
        {
          "counter": "gitlab_add_mr_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 Sage MCP, apply this rule, and every gitlab_add_mr_note call is checked against it from then on.

FAQ

Questions about gitlab_add_mr_note

What does the gitlab_add_mr_note tool do? +

Add a note (comment) to a merge request. It is categorised as a Write tool in the Sage 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 gitlab_add_mr_note? +

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

What risk level is gitlab_add_mr_note? +

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

Can I rate-limit gitlab_add_mr_note? +

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

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

gitlab_add_mr_note is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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