Critical-risk tools in MCP Gitlab

Critical severity MCP Gitlab MCP Server 7 of 63 tools

7 of the 63 tools in MCP Gitlab are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.

Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.

Tools at critical risk

cancel_job_tool Destructive

Cancel a running CI/CD job.
cancel_pipeline_tool Destructive

Cancel a running CI/CD pipeline.
delete_branch_tool Destructive

Delete a branch from a GitLab repository.
delete_job_tool Destructive

Delete a CI/CD job's artifacts and trace log.
delete_label_tool Destructive

Delete a label from a GitLab project.
delete_pipeline_tool Destructive

Delete a CI/CD pipeline and all its jobs permanently.
delete_project_tool Destructive

Delete a GitLab project permanently.

Attacks that target this class

Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.

Destructive Action Autonomy
Privilege escalation via admin-only tools
Data exfiltration via tool chaining
Runaway Tool Loops

Critical-risk tools in MCP Gitlab

Tools at critical risk

Attacks that target this class

More on MCP Gitlab

Enforce policy on every MCP Gitlab tool call.