retry_pipeline · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What retry_pipeline does on Mcp Gitlab

AI agents invoke retry_pipeline 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 retry_pipeline needs a policy

Retrying a pipeline triggers external compute jobs, deployments, and side-effects depending on pipeline contents. This is an Execute-category action with high blast radius since pipelines can deploy code, modify infrastructure, or run arbitrary scripts.

From the tool's definition 'Retry a failed pipeline' — re-triggers CI/CD pipeline execution; 'dry_run=true by default' confirms real execution is possible

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_pipeline Rate-limited

retry_pipeline 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": {
    "retry_pipeline": {
      "limits": [
        {
          "counter": "retry_pipeline_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 retry_pipeline

What does the retry_pipeline tool do? +

Retry a failed pipeline. dry_run=true by default. 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 retry_pipeline? +

Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for retry_pipeline: 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 retry_pipeline? +

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

Can I rate-limit retry_pipeline? +

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

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

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

// THE FULL RECORD

retry_pipeline is one line of Mcp Gitlab's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →