// SCAN REPORT

Qodev Gitlab

18 tools. 17 can modify or destroy data without limits.

17 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

17 can modify or destroy data

1 read-only

18 tools total

Community server · catalogue entry verified 02/07/2026

How to control Qodev Gitlab ↓

TOOL MAP

What Qodev Gitlab exposes to your agents

Read (1) Write / Execute (17) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Qodev Gitlab tools

Execute · Medium wait_for_pipeline This tool likely executes a blocking operation that monitors an external system (GitLab's CI/CD pipeline), which qualifies as Execute rather than Read. Execute · High merge_merge_request Merging a merge request is an execution-level operation that combines branches, potentially modifying the main/protected branch of a repository. Execute · High retry_job Based on the tool name and GitLab integration context, 'retry_job' most likely re-executes a failed or cancelled CI/CD pipeline job. Write · Medium close_issue Closing an issue modifies state but is not destructive—it can be undone by reopening.

17 of Qodev Gitlab's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Qodev Gitlab

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

Rate limit write operations

{
  "close_issue": {
    "limits": [
      {
        "counter": "close_issue_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "download_artifact": {
    "limits": [
      {
        "counter": "download_artifact_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 Qodev 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 QODEV GITLAB →

Instant setup, no code required.

FULL CATALOGUE

All 18 Qodev Gitlab tools

EXECUTE 3 tools

Execute merge_merge_request merge_merge_request Execute retry_job retry_job Execute wait_for_pipeline wait_for_pipeline

WRITE 14 tools

Write close_issue close_issue Write close_merge_request close_merge_request Write comment_on_issue comment_on_issue Write comment_on_merge_request comment_on_merge_request Write create_inline_comment create_inline_comment Write create_issue create_issue Write create_merge_request create_merge_request Write create_release create_release Write reply_to_discussion reply_to_discussion Write resolve_discussion_thread resolve_discussion_thread Write set_project_ci_variable set_project_ci_variable Write update_issue update_issue Write update_merge_request update_merge_request Write upload_file upload_file

READ 1 tools

Read download_artifact download_artifact

EXPLORE

Related servers

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

FAQ

Questions about Qodev Gitlab

How do I prevent bulk modifications through Qodev Gitlab? +

The Qodev Gitlab server has 14 write tools including close_issue, close_merge_request, comment_on_issue. 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 Qodev Gitlab.

How many tools does the Qodev Gitlab MCP server expose? +

18 tools across 3 categories: Execute, Read, Write. 1 are read-only. 17 can modify, create, or delete data.

How do I enforce a policy on Qodev Gitlab? +

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

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

ENFORCE POLICY ON QODEV GITLAB →

Instant setup, no code required.

18 Qodev Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.