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.
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.
Documented attack patterns abuse exactly the kind of access gitlab_add_mr_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_add_mr_note:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_add_mr_note": {
"limits": [
{
"counter": "gitlab_add_mr_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
gitlab_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 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.
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.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.