set_project_ci_variable · Qodev Gitlab MCP: Risk & Policy

WHAT IT DOES

What set_project_ci_variable does on Qodev Gitlab

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

WHY IT NEEDS A POLICY

Why set_project_ci_variable needs a policy

Setting CI/CD variables modifies project configuration reversibly. This is a Write operation rather than Execute (which would run arbitrary code) or Destructive (which would delete data). However, CI variables often contain secrets and control build behavior, making misuse high-severity.

From the tool's definition Tool name 'set_project_ci_variable' indicates creation or modification of CI/CD variables at the project level. Sibling tools like 'create_issue' and 'create_merge_request' confirm this server handles write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_project_ci_variable Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_project_ci_variable": {
      "limits": [
        {
          "counter": "set_project_ci_variable_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Qodev Gitlab, so you can run agents against it safely.

FAQ

Questions about set_project_ci_variable

What does the set_project_ci_variable tool do? +

set_project_ci_variable. It is categorised as a Write tool in the Qodev 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 set_project_ci_variable? +

Register the Qodev Gitlab MCP server in PolicyLayer and add a rule for set_project_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 Qodev Gitlab. Nothing to install.

What risk level is set_project_ci_variable? +

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

Can I rate-limit set_project_ci_variable? +

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

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

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