get_project_variable
Get a single CI/CD variable from a project
This record as markdown: /tools/io-github-zereight-gitlab-mcp/get-project-variable.md
What get_project_variable does on Gitlab Mcp
AI agents call get_project_variable to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_project_variable is rated Low
This tool retrieves existing configuration data (a CI/CD variable) without creating, modifying, or deleting anything. It is a straightforward read operation. Severity is low because exposure of CI/CD variables could be a concern in some contexts, but the tool itself performs no destructive or harmful action—the risk depends entirely on what data the variable contains and whether the user has legitimate access to…
From the tool's definition The tool name is 'get_project_variable' and the description states it 'Get[s] a single CI/CD variable from a project'. The verb 'get' and the absence of any modification language indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_project_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 get_project_variable, this is the rule to start with:
get_project_variable 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 Mcp, apply this rule, and every get_project_variable call is checked against it from then on.
Questions about get_project_variable
Get a single CI/CD variable from a project. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for get_project_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.
get_project_variable 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 get_project_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 get_project_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.
get_project_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