// SCAN REPORT

GitLab MCP Server

42 tools. 19 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

19 can modify or destroy data

23 read-only

42 tools total

Community server · catalogue entry verified 11/06/2026

How to control GitLab MCP Server ↓

TOOL MAP

What GitLab MCP Server exposes to your agents

Read (23) Write / Execute (16) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous GitLab MCP Server tools

Destructive · High gitlab_delete_cicd_variable The tool performs irreversible deletion of CI/CD variables, which are critical infrastructure components used in deployment pipelines. Destructive · High gitlab_delete_trigger_token This tool irreversibly deletes a CI/CD pipeline trigger token, which is a sensitive authentication credential. Destructive · High gitlab_delete_webhook Deleting a webhook irreversibly removes a configured integration endpoint. Execute · High gitlab_trigger_pipeline Triggering a GitLab pipeline is an Execute action because it initiates external operations (builds, tests, deployments) whose outcomes depend on the pipeline configuration and commit being tested.

19 of GitLab MCP Server's 42 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GitLab MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "gitlab_delete_cicd_variable": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "gitlab_add_group_member": {
    "limits": [
      {
        "counter": "gitlab_add_group_member_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "gitlab_compare_branches": {
    "limits": [
      {
        "counter": "gitlab_compare_branches_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register GitLab MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GITLAB →

Free to start. No card required.

FULL CATALOGUE

All 42 GitLab MCP Server tools

DESTRUCTIVE 3 tools

Destructive gitlab_delete_cicd_variable Delete a CI/CD variable Destructive gitlab_delete_trigger_token Delete a pipeline trigger token Destructive gitlab_delete_webhook Delete a webhook

EXECUTE 2 tools

Execute gitlab_trigger_pipeline Trigger a pipeline run Execute gitlab_test_webhook Test a webhook

WRITE 14 tools

Write gitlab_add_group_member Add a user to a group Write gitlab_add_project_member Add a user to a project Write gitlab_add_webhook Add a new webhook to a project Write gitlab_create_cicd_variable Create a new CI/CD variable Write gitlab_create_merge_request Create a new merge request in a GitLab project Write gitlab_create_merge_request_note Add a comment to a merge request Write gitlab_create_merge_request_note_internal Add a comment to a merge request with option to make it an internal note Write gitlab_create_trigger_token Create a new pipeline trigger token Write gitlab_disable_slack_integration Disable Slack integration for a project Write gitlab_update_cicd_variable Update a CI/CD variable Write gitlab_update_merge_request Update a merge request title and description Write gitlab_update_slack_integration Update Slack integration settings for a project Write gitlab_update_trigger_token Update a pipeline trigger token Write gitlab_update_webhook Update an existing webhook

READ 23 tools

Read gitlab_compare_branches Compare branches, tags or commits Read gitlab_get_cicd_variable Get a specific CI/CD variable Read gitlab_get_group Get details of a specific group Read gitlab_get_integration Get integration details for a project Read gitlab_get_merge_request Get details of a specific merge request Read gitlab_get_merge_request_changes Get changes (diff) of a specific merge request Read gitlab_get_project Get details of a specific GitLab project Read gitlab_get_repository_file Get content of a file in a repository Read gitlab_get_trigger_token Get details of a pipeline trigger token Read gitlab_get_user Get details of a specific user Read gitlab_get_webhook Get details of a specific webhook Read gitlab_list_branches List branches of a GitLab project Read gitlab_list_cicd_variables List CI/CD variables for a project Read gitlab_list_group_members List members of a group Read gitlab_list_groups List GitLab groups Read gitlab_list_integrations List all available project integrations/services Read gitlab_list_issues List issues in a GitLab project Read gitlab_list_merge_requests List merge requests in a GitLab project Read gitlab_list_project_members List members of a project Read gitlab_list_projects List GitLab projects accessible to the user Read gitlab_list_trigger_tokens List pipeline trigger tokens Read gitlab_list_users List GitLab users Read gitlab_list_webhooks List webhooks for a project

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about GitLab MCP Server

Can an AI agent delete data through the GitLab MCP Server MCP server? +

Yes. The GitLab MCP Server server exposes 3 destructive tools including gitlab_delete_cicd_variable, gitlab_delete_trigger_token, gitlab_delete_webhook. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through GitLab MCP Server? +

The GitLab MCP Server server has 14 write tools including gitlab_add_group_member, gitlab_add_project_member, gitlab_add_webhook. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach GitLab MCP Server.

How many tools does the GitLab MCP Server MCP server expose? +

42 tools across 4 categories: Destructive, Execute, Read, Write. 23 are read-only. 19 can modify, create, or delete data.

How do I enforce a policy on GitLab MCP Server? +

Register the GitLab MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GitLab MCP Server tool call.

Deterministic rules across all 42 GitLab MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GITLAB →

Free to start. No card required.

42 GitLab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.