transfer_project · GitLab MCP Server MCP: Risk & Policy

WHAT IT DOES

What transfer_project does on GitLab MCP Server

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

Transferring a project changes its location/ownership within GitLab, which is a significant write operation. While potentially reversible by an admin, it changes access controls, URLs, and group membership. It doesn't delete data but can break integrations, CI/CD pipelines, and existing links.

From the tool's definition Transfer a project to a new namespace

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transfer_project Rate-limited

transfer_project 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": {
    "transfer_project": {
      "limits": [
        {
          "counter": "transfer_project_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 transfer_project

What does the transfer_project tool do? +

Transfer a project to a new namespace. 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 transfer_project? +

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

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

Can I rate-limit transfer_project? +

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

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

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