create_file_tool · MCP Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_file_tool does on MCP Gitlab

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

File creation is a write operation that modifies repository state but is reversible (files can be deleted). It is not destructive since deletion is possible, not financial, and does not execute arbitrary code. Severity is high because creating files in a repository could introduce malicious code, overwrite critical configuration, or affect deployment pipelines if the agent misuses this without proper validation.

From the tool's definition Tool name is 'create_file_tool' which performs file creation. Sibling tools on the GitLab MCP server include create_branch_tool, create_issue_tool, create_merge_request_tool, and create_label_tool—all write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_file_tool Rate-limited

create_file_tool 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_file_tool": {
      "limits": [
        {
          "counter": "create_file_tool_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 create_file_tool

What does the create_file_tool tool do? +

create_file_tool. 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 create_file_tool? +

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

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

Can I rate-limit create_file_tool? +

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

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

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