create_merge_request · Helm Chart CLI MCP: Risk & Policy

WHAT IT DOES

What create_merge_request does on Helm Chart CLI

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

WHY IT NEEDS A POLICY

Why create_merge_request needs a policy

This tool creates (writes) a new merge request artifact in GitLab, which is a standard git workflow object. While merge requests can trigger CI/CD pipelines or other automated processes, the direct action is creating/writing metadata in GitLab. The operation is reversible (the MR can be closed/deleted). It does not execute arbitrary code, delete data permanently, or move money.

From the tool's definition Tool name is 'create_merge_request' and description states it will 'Create a new merge request in a GitLab project'. This creates a new code review object in GitLab, which is a reversible modification to the version control system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_merge_request Rate-limited

create_merge_request 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_merge_request": {
      "limits": [
        {
          "counter": "create_merge_request_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 Helm Chart CLI, so you can run agents against it safely.

FAQ

Questions about create_merge_request

What does the create_merge_request tool do? +

Create a new merge request in a GitLab project. It is categorised as a Write tool in the Helm Chart CLI 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_merge_request? +

Register the Helm Chart CLI MCP server in PolicyLayer and add a rule for create_merge_request: 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 Helm Chart CLI. Nothing to install.

What risk level is create_merge_request? +

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

Can I rate-limit create_merge_request? +

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

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

create_merge_request is provided by the Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.