add_merge_request_comment · Kepler MCP GitLab Server MCP

WHAT IT DOES

What add_merge_request_comment does on Kepler MCP GitLab Server

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

WHY IT NEEDS A POLICY

Why add_merge_request_comment needs a policy

This tool creates new data (a comment) on an existing merge request resource. It is reversible and has no destructive capability. The medium severity reflects that while comments themselves are non-destructive, a compromised AI agent could spam, harass, or inject misleading information into MR discussions, affecting team workflows and decisions.

From the tool's definition Tool name 'add_merge_request_comment' indicates creating/appending a comment to a merge request. The empty description limits certainty, but sibling tools like 'add_issue_comment' and 'create_merge_request' establish the pattern of write operations on GitLab…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_merge_request_comment Rate-limited

add_merge_request_comment 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": {
    "add_merge_request_comment": {
      "limits": [
        {
          "counter": "add_merge_request_comment_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 Kepler MCP GitLab Server, so you can run agents against it safely.

FAQ

Questions about add_merge_request_comment

What does the add_merge_request_comment tool do? +

add_merge_request_comment. It is categorised as a Write tool in the Kepler MCP GitLab 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 add_merge_request_comment? +

Register the Kepler MCP GitLab Server MCP server in PolicyLayer and add a rule for add_merge_request_comment: 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 Kepler MCP GitLab Server. Nothing to install.

What risk level is add_merge_request_comment? +

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

Can I rate-limit add_merge_request_comment? +

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

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

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