create_repository · GitLab MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_repository does on GitLab MCP Server

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

WHY IT NEEDS A POLICY

Why create_repository needs a policy

This tool creates a new project resource in GitLab, which is a write operation that adds data to the system. While the action is reversible (the project can be deleted), it does create a new persistent entity and consumes resources. The severity is medium because an AI agent abusing this could spam the GitLab instance with many projects, but this is less damaging than destructive or financial operations.

From the tool's definition Tool name is 'create_repository' and description states it will 'Create a new GitLab project'. Creating a new project is a reversible write operation that modifies the state of the GitLab instance by adding a new resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_repository Rate-limited

create_repository 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_repository": {
      "limits": [
        {
          "counter": "create_repository_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 Server, so you can run agents against it safely.

FAQ

Questions about create_repository

What does the create_repository tool do? +

Create a new GitLab project. It is categorised as a Write tool in the GitLab MCP Server 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_repository? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for create_repository: 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 Server. Nothing to install.

What risk level is create_repository? +

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

Can I rate-limit create_repository? +

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

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

create_repository is provided by the GitLab MCP Server MCP server (martijndormans/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.