add_issue_note · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What add_issue_note does on Mcp Gitlab

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

WHY IT NEEDS A POLICY

Why add_issue_note needs a policy

Adding a note/comment to an issue creates new data in a reversible manner (comments can be edited or deleted by authorized users), fitting the Write category. Severity is medium because while comment creation is not destructive, it affects issue tracking and team communication, and a malicious agent could spam or post misleading comments.

From the tool's definition Tool name 'add_issue_note' and description 'Ajouter un commentaire sur une issue' (Add a comment on an issue) directly indicates creation of new comment data on an existing issue. The server description mentions 'dry-run safety' as a built-in control.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_issue_note Rate-limited

add_issue_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": {
    "add_issue_note": {
      "limits": [
        {
          "counter": "add_issue_note_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 Mcp Gitlab, so you can run agents against it safely.

FAQ

Questions about add_issue_note

What does the add_issue_note tool do? +

Ajouter un commentaire sur une issue. Par defaut dry_run=true. 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.

How do I enforce a policy on add_issue_note? +

Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for add_issue_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.

What risk level is add_issue_note? +

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

Can I rate-limit add_issue_note? +

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

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

add_issue_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.