create_inline_comment · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_inline_comment does on Qodev Gitlab

AI agents use create_inline_comment to create or update resources in Qodev Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qodev Gitlab environment.

WHY IT NEEDS A POLICY

Why create_inline_comment needs a policy

The tool creates (writes) a new inline comment, a reversible operation that modifies a merge request or code review by adding commentary. This is categorized as Write rather than Read (retrieves data) or Execute (triggers external operations with unpredictable effects). While the description is empty, the tool name and server context provide sufficient justification.

From the tool's definition Tool name 'create_inline_comment' indicates creation of comment data. Sibling tools like 'comment_on_issue' and 'comment_on_merge_request' establish that this server creates comments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_inline_comment Rate-limited

create_inline_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": {
    "create_inline_comment": {
      "limits": [
        {
          "counter": "create_inline_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 Qodev Gitlab, so you can run agents against it safely.

FAQ

Questions about create_inline_comment

What does the create_inline_comment tool do? +

create_inline_comment. It is categorised as a Write tool in the Qodev 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 create_inline_comment? +

Register the Qodev Gitlab MCP server in PolicyLayer and add a rule for create_inline_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 Qodev Gitlab. Nothing to install.

What risk level is create_inline_comment? +

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

Can I rate-limit create_inline_comment? +

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

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

create_inline_comment is provided by the Qodev Gitlab MCP server (qodevai/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.