// SCAN REPORT

Gitlab

56 tools. 28 can modify or destroy data without limits.

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

Last updated: 14 Aug 2026

28 can modify or destroy data

28 read-only

56 tools total

Community server · catalogue entry checked 14/08/2026

How to control Gitlab ↓

TOOL MAP

What Gitlab exposes to your agents

Read (28) Write / Execute (22) Destructive / Financial (6)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Gitlab tools

Destructive · High gitlab_delete_branch Deleting a branch is a destructive action that irreversibly removes code and commit history. Destructive · High gitlab_delete_ci_variable This tool irreversibly removes CI/CD variables, which are critical configuration assets used in pipelines. Destructive · High gitlab_delete_group_variable This tool permanently removes configuration data (CI/CD variables) without possibility of recovery through the tool itself. Destructive · Critical gitlab_revoke_group_access_token Revoking an access token is an irreversible destructive action.

28 of Gitlab's 56 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

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

Deny destructive operations

{
  "gitlab_delete_branch": {
    "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

{
  "add_environment_promotion": {
    "limits": [
      {
        "counter": "add_environment_promotion_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_pipeline_failure": {
    "limits": [
      {
        "counter": "analyze_pipeline_failure_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 — 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 →

Instant setup, no code required.

FULL CATALOGUE

All 56 Gitlab tools

DESTRUCTIVE 6 tools

Destructive gitlab_delete_branch Delete a branch. Refuses to delete protected branches. Destructive gitlab_delete_ci_variable Delete a CI/CD variable from a project. Destructive gitlab_delete_group_variable Delete a CI/CD variable from a group. Destructive gitlab_revoke_group_access_token gitlab_revoke_group_access_token Destructive gitlab_revoke_personal_access_token gitlab_revoke_personal_access_token Destructive gitlab_revoke_project_access_token Revoke (delete) a project access token. IRREVERSIBLE.

EXECUTE 4 tools

Execute gitlab_cancel_pipeline Cancel a running pipeline. Execute gitlab_register_local_runner gitlab_register_local_runner Execute gitlab_retry_pipeline Retry failed jobs in a pipeline. Execute gitlab_trigger_pipeline Trigger a GitLab CI/CD pipeline on a branch.

WRITE 18 tools

Write add_environment_promotion add_environment_promotion Write add_security_stages add_security_stages Write add_terraform_stages add_terraform_stages Write apply_fix_to_ci apply_fix_to_ci Write generate_ci_config generate_ci_config Write gitlab_batch_commit gitlab_batch_commit Write gitlab_create_branch gitlab_create_branch Write gitlab_create_ci_variable gitlab_create_ci_variable Write gitlab_create_group gitlab_create_group Write gitlab_create_group_access_token gitlab_create_group_access_token Write gitlab_create_group_variable gitlab_create_group_variable Write gitlab_create_issue_from_vuln gitlab_create_issue_from_vuln Write gitlab_create_mr gitlab_create_mr Write gitlab_create_or_update_file gitlab_create_or_update_file Write gitlab_create_project gitlab_create_project Write gitlab_create_project_access_token gitlab_create_project_access_token Write gitlab_merge_mr gitlab_merge_mr Write gitlab_update_runner_tags Update the tag list for a runner.

READ 28 tools

Read analyze_pipeline_failure Analyze a failed pipeline: fetch all failed job logs, classify errors, return root-cause report. Read gitlab_clone_repo gitlab_clone_repo Read gitlab_get_file Read a file from the repository at any branch or commit. Read gitlab_get_job_logs Fetch logs from a CI/CD job. Returns the last N lines. Read gitlab_get_mr_diff Show the file diff of a merge request. Read gitlab_get_pipeline_artifacts Download artifacts from a completed job. Read gitlab_get_pipeline_jobs List all jobs in a pipeline with their status and stage. Read gitlab_get_pipeline_status gitlab_get_pipeline_status Read gitlab_get_project Get detailed information about a GitLab project. Read gitlab_get_runner_status Check a runner's health, version, and last contact time. Read gitlab_get_security_report gitlab_get_security_report Read gitlab_get_security_summary Get a unified security summary across all scan types from a pipeline. Read gitlab_list_branches List all branches in a project with protection status and last commit info. Read gitlab_list_ci_variables List all CI/CD variables for a project. Values are NOT returned for masked variables. Read gitlab_list_group_access_tokens List all access tokens on a group. Token values are NOT returned — only metadata Read gitlab_list_group_variables List all CI/CD variables set at the group level. Read gitlab_list_groups List GitLab groups and subgroups you have access to. Read gitlab_list_mrs List merge requests in a project. Read gitlab_list_personal_access_tokens List YOUR OWN personal access tokens (the user the GITLAB_TOKEN authenticates as). Read gitlab_list_pipelines gitlab_list_pipelines Read gitlab_list_project_access_tokens List all access tokens on a project. Token values are NOT returned — only metadata. Read gitlab_list_projects List GitLab projects you have access to. Read gitlab_list_runners gitlab_list_runners Read gitlab_list_vulnerabilities gitlab_list_vulnerabilities Read gitlab_pause_runner Pause or unpause a runner. Read suggest_fix suggest_fix Read trace_deploy_failure trace_deploy_failure Read validate_ci_config Lint a .gitlab-ci.yml using GitLab's API validator.

EXPLORE

Related servers

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

FAQ

Questions about Gitlab

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

Yes. The Gitlab server exposes 6 destructive tools including gitlab_delete_branch, gitlab_delete_ci_variable, gitlab_delete_group_variable. 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? +

The Gitlab server has 18 write tools including add_environment_promotion, add_security_stages, add_terraform_stages. 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.

How many tools does the Gitlab MCP server expose? +

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

How do I enforce a policy on Gitlab? +

Register the Gitlab 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 tool call.

Deterministic rules across all 56 Gitlab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GITLAB →

Instant setup, no code required.

56 Gitlab tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Gitlab's registry record.

The record behind this page: 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 →