New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_delete_group_variable

Delete a CI/CD variable from a group.

SERVERGitlab SOURCEdkeeno/gitlab-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-delete-group-variable.md

What gitlab_delete_group_variable does on Gitlab

AI agents call gitlab_delete_group_variable to permanently remove resources in Gitlab, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why gitlab_delete_group_variable is rated Critical

This tool permanently removes configuration data (CI/CD variables) without possibility of recovery through the tool itself. CI/CD variables frequently store credentials and secrets critical to deployment pipelines. Misuse by an AI agent could disable production deployments or expose security weaknesses by removing protective secrets.

From the tool's definition Tool name contains 'delete' and description states 'Delete a CI/CD variable from a group.' CI/CD variables often contain sensitive credentials, API keys, and secrets. Deletion is irreversible.

Questions about gitlab_delete_group_variable

What does the gitlab_delete_group_variable tool do? +

Delete a CI/CD variable from a group. It is categorised as a Destructive tool in the Gitlab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gitlab_delete_group_variable? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_delete_group_variable: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Gitlab. Nothing to install.

What risk level is gitlab_delete_group_variable? +

gitlab_delete_group_variable is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gitlab_delete_group_variable? +

Yes. Add a rate_limit block to the gitlab_delete_group_variable rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block gitlab_delete_group_variable completely? +

Set action: deny in the PolicyLayer policy for gitlab_delete_group_variable. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides gitlab_delete_group_variable? +

gitlab_delete_group_variable is provided by the Gitlab MCP server (dkeeno/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gitlab, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.