create_pipeline_tool · MCP Gitlab MCP: Risk & Policy

WHAT IT DOES

What create_pipeline_tool does on MCP Gitlab

AI agents invoke create_pipeline_tool to trigger actions in MCP Gitlab. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create_pipeline_tool needs a policy

Triggering a CI/CD pipeline executes automated workflows that can run arbitrary code, deploy software, modify infrastructure, or perform other operations with significant blast radius. This is an Execute-category action — it initiates external operations whose effects depend on the pipeline's contents.

From the tool's definition Create (trigger) a new CI/CD pipeline

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_pipeline_tool Rate-limited

create_pipeline_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_pipeline_tool": {
      "limits": [
        {
          "counter": "create_pipeline_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_pipeline_tool

What does the create_pipeline_tool tool do? +

Create (trigger) a new CI/CD pipeline. It is categorised as a Execute tool in the MCP Gitlab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_pipeline_tool? +

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

What risk level is create_pipeline_tool? +

create_pipeline_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_pipeline_tool? +

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

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

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