comment_issue · GitLab MCP: Risk & Policy

WHAT IT DOES

What comment_issue does on GitLab MCP

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

WHY IT NEEDS A POLICY

Why comment_issue needs a policy

Adding a comment is a reversible write operation that creates new data in the GitLab system. It does not execute arbitrary code, delete data, or move money. While comments can be edited or deleted later, the tool itself performs a create/post operation.

From the tool's definition The tool name is 'comment_issue' and the description states it will 'Add a comment (note) to an issue.' This creates new data (a comment) within an existing issue.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

comment_issue Rate-limited

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

FAQ

Questions about comment_issue

What does the comment_issue tool do? +

Add a comment (note) to an issue. 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 comment_issue? +

Register the GitLab MCP server in PolicyLayer and add a rule for comment_issue: 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 comment_issue? +

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

Can I rate-limit comment_issue? +

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

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

comment_issue is provided by the GitLab MCP server (shahabmosavi/gitlab_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.