Add a comment to a merge request. dry_run=true by default.
AI agents use add_mr_note to create or update resources in Mcp Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitlab environment.
Adding a note/comment to a merge request creates new data (the comment) but is fully reversible—comments can be edited or deleted. This is a standard Write operation. The dry-run default adds an extra safety layer. The low severity reflects minimal blast radius: a misused comment is easily corrected and cannot affect system integrity or data loss.
From the tool's definition Tool description: 'Add a comment to a merge request.' Comments are reversible modifications to data; they do not delete, execute code, or move funds. The note about 'dry_run=true by default' confirms this is a safe, non-destructive operation.
Attacks that exploit this kind of access
Add a comment to a merge request. dry_run=true by default. It is categorised as a Write tool in the Mcp Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for 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 Mcp Gitlab. Nothing to install.
add_mr_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
add_mr_note is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →