gitlab_delete_ci_variable
Delete a CI/CD variable from a project.
This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-delete-ci-variable.md
What gitlab_delete_ci_variable does on Gitlab
AI agents call gitlab_delete_ci_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_ci_variable is rated Critical
This tool irreversibly removes CI/CD variables, which are critical configuration assets used in pipelines. Deletion is permanent and cannot be undone through normal means. While not as severe as deleting entire repositories, removing CI/CD variables can break pipelines, expose secrets if improperly managed, or disrupt deployments.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a CI/CD variable from a project.' CI/CD variables are configuration data that cannot be recovered once deleted.
Attacks that exploit this kind of access
The rule that runs gitlab_delete_ci_variable safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_delete_ci_variable, this is the rule to start with:
gitlab_delete_ci_variable is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab, apply this rule, and every gitlab_delete_ci_variable call is checked against it from then on.
Questions about gitlab_delete_ci_variable
Delete a CI/CD variable from a project. 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.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_delete_ci_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.
gitlab_delete_ci_variable is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gitlab_delete_ci_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.
Set action: deny in the PolicyLayer policy for gitlab_delete_ci_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.
gitlab_delete_ci_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.
Across the catalogue