create_or_update_file · GitLab MCP: Risk & Policy

WHAT IT DOES

What create_or_update_file does on GitLab MCP

AI agents use create_or_update_file 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 create_or_update_file needs a policy

This tool creates or modifies files in a repository through a commit operation. While the action is reversible (files can be reverted via git operations), the ability to overwrite existing files and commit changes directly to a repository represents a significant write capability.

From the tool's definition Tool description states it can 'Create (or, with ``update=True``, overwrite) a single file in one commit.' This is reversible modification of repository content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_or_update_file Rate-limited

create_or_update_file 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_or_update_file": {
      "limits": [
        {
          "counter": "create_or_update_file_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 create_or_update_file

What does the create_or_update_file tool do? +

Create (or, with update=True, overwrite) a single file in one commit. 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 create_or_update_file? +

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

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

Can I rate-limit create_or_update_file? +

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

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

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

// THE FULL RECORD

create_or_update_file is one line of GitLab's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →