gitlab_list_ci_variables
List all CI/CD variables for a project. Values are NOT returned for masked variables.
This record as markdown: /tools/dkeeno-gitlab-mcp-server/gitlab-list-ci-variables.md
What gitlab_list_ci_variables does on Gitlab
AI agents call gitlab_list_ci_variables to retrieve information from Gitlab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gitlab_list_ci_variables is rated Low
This tool retrieves or queries CI/CD variable metadata without modifying, deleting, or executing any operations. Even though CI variables may contain sensitive information, the tool explicitly prevents exposure of masked variable values, limiting the data returned to non-sensitive metadata. The action is purely informational with no capability to alter state.
From the tool's definition Tool name 'gitlab_list_ci_variables' and description 'List all CI/CD variables for a project' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs gitlab_list_ci_variables 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_list_ci_variables, this is the rule to start with:
gitlab_list_ci_variables is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab, apply this rule, and every gitlab_list_ci_variables call is checked against it from then on.
Questions about gitlab_list_ci_variables
List all CI/CD variables for a project. Values are NOT returned for masked variables. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_list_ci_variables: 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_list_ci_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gitlab_list_ci_variables 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_list_ci_variables. 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_list_ci_variables 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.
This server
Across the catalogue