update_group_variable
Update an existing CI/CD variable in a group
This record as markdown: /tools/io-github-zereight-gitlab-mcp/update-group-variable.md
What update_group_variable does on Gitlab Mcp
AI agents use update_group_variable to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.
Why update_group_variable is rated Medium
This tool performs a reversible modification (update) of CI/CD variables at the group level. CI/CD variables often contain sensitive data like API keys and secrets, making unauthorized updates a medium-severity risk. The effect is reversible (can be updated again), so it does not qualify as Destructive.
From the tool's definition Tool name and description: 'Update an existing CI/CD variable in a group' — modifies group-level CI/CD variables which are configuration settings used across pipelines.
Attacks that exploit this kind of access
The rule that runs update_group_variable safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_group_variable, this is the rule to start with:
update_group_variable stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every update_group_variable call is checked against it from then on.
Questions about update_group_variable
Update an existing CI/CD variable in a group. It is categorised as a Write tool in the Gitlab Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for update_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 Mcp. Nothing to install.
update_group_variable is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_group_variable is provided by the Gitlab MCP server (@zereight/mcp-gitlab). 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.
This server
Across the catalogue