add_terraform_stages
A write tool on the Gitlab MCP server.
This record as markdown: /tools/dkeeno-gitlab-mcp-server/add-terraform-stages.md
What add_terraform_stages does on Gitlab
AI agents use add_terraform_stages 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 add_terraform_stages is rated Medium
The tool name indicates it adds (modifies/writes) Terraform-related stages to a pipeline. This is a reversible Write action—pipeline stages can be added or removed. It does not execute arbitrary code (Execute), delete irreversibly (Destructive), or move money (Financial). The high severity reflects that misconfigured pipeline stages could affect deployment processes across infrastructure.
From the tool's definition Tool name 'add_terraform_stages' and sibling tools like 'add_environment_promotion' and 'add_security_stages' operate on pipeline configurations.
Attacks that exploit this kind of access
The rule that runs add_terraform_stages 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 add_terraform_stages, this is the rule to start with:
add_terraform_stages 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, apply this rule, and every add_terraform_stages call is checked against it from then on.
Questions about add_terraform_stages
add_terraform_stages 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.
Register the Gitlab MCP server in PolicyLayer and add a rule for add_terraform_stages: 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.
add_terraform_stages 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 add_terraform_stages 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 add_terraform_stages. 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.
add_terraform_stages 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