Critical Risk →

gitlab_delete_cicd_variable

Delete a CI/CD variable

How to control gitlab_delete_cicd_variable ↓

What gitlab_delete_cicd_variable does on GitLab MCP Server

AI agents call gitlab_delete_cicd_variable to permanently remove resources in GitLab MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why gitlab_delete_cicd_variable needs a policy

The tool performs irreversible deletion of CI/CD variables, which are critical infrastructure components used in deployment pipelines. Unauthorized deletion could break builds, deployments, or expose secrets management failures.

From the tool's definition Tool name explicitly uses "delete" and description states "Delete a CI/CD variable". CI/CD variables are configuration settings that cannot be trivially recreated and their deletion is irreversible.

Documented attack patterns abuse exactly the kind of access gitlab_delete_cicd_variable gives an agent:

How to control gitlab_delete_cicd_variable

PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_delete_cicd_variable:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "gitlab_delete_cicd_variable"
  ]
}

gitlab_delete_cicd_variable disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GitLab MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about gitlab_delete_cicd_variable

What does the gitlab_delete_cicd_variable tool do? +

Delete a CI/CD variable. It is categorised as a Destructive tool in the GitLab MCP Server 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_cicd_variable? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for gitlab_delete_cicd_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 MCP Server. Nothing to install.

What risk level is gitlab_delete_cicd_variable? +

gitlab_delete_cicd_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_cicd_variable? +

Yes. Add a rate_limit block to the gitlab_delete_cicd_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_cicd_variable completely? +

Set action: deny in the PolicyLayer policy for gitlab_delete_cicd_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_cicd_variable? +

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

Enforce policy on every GitLab MCP Server tool call.

Start from GitLab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

42 GitLab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.