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

gitlab_create_ci_variable

A write tool on the Gitlab MCP server.

SERVERGitlab SOURCEdkeeno/gitlab-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-create-ci-variable.md

What gitlab_create_ci_variable does on Gitlab

AI agents use gitlab_create_ci_variable to create or update resources in Gitlab, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab environment.

Why gitlab_create_ci_variable is rated Medium

Creating CI variables is a Write operation—it creates new configuration data that persists and affects pipeline behavior. However, severity is 'high' rather than 'medium' because CI variables frequently store sensitive credentials (API keys, tokens, passwords); an agent could maliciously inject secrets or misconfigure deployments.

From the tool's definition Tool name 'gitlab_create_ci_variable' indicates creation of CI/CD variables in GitLab. CI variables are configuration data that can include secrets, credentials, and environment-specific values.

Questions about gitlab_create_ci_variable

What does the gitlab_create_ci_variable tool do? +

gitlab_create_ci_variable is a write tool on the Gitlab MCP server. It is categorised as a Write tool in the Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gitlab_create_ci_variable? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_create_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.

What risk level is gitlab_create_ci_variable? +

gitlab_create_ci_variable is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gitlab_create_ci_variable? +

Yes. Add a rate_limit block to the gitlab_create_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.

How do I block gitlab_create_ci_variable completely? +

Set action: deny in the PolicyLayer policy for gitlab_create_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.

What MCP server provides gitlab_create_ci_variable? +

gitlab_create_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.

// 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.