Critical-risk tools in GitLab Operations
6 of the 22 tools in GitLab Operations 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
-
delete_ci_variableDestructive 4/5Remove a CI/CD variable from a project by key
-
delete_groupDestructive 4/5Delete a GitLab group and all projects within it (cascading delete)
-
delete_pipeline_triggerDestructive 4/5Remove a pipeline trigger token, preventing any further pipeline triggers using it
-
delete_webhookDestructive 4/5Remove a webhook from a GitLab project
-
revoke_project_access_tokenDestructive 4/5Revoke a project access token, immediately invalidating it for all future API requests
-
unprotect_branchDestructive 4/5Remove protection rules from a branch, restoring default push and merge permissions
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.
More on GitLab Operations
Enforce policy on GitLab Operations
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init