cancel_pipeline_job

Cancel a running pipeline job

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/cancel-pipeline-job.md

WHAT IT DOES

What cancel_pipeline_job does on Gitlab Mcp

AI agents call cancel_pipeline_job to permanently remove resources in Gitlab Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cancel_pipeline_job is rated Critical

Cancelling a running pipeline job is an irreversible action — the job cannot be resumed from where it stopped. It terminates an active CI/CD process, potentially disrupting deployments, tests, or builds that cannot be automatically recovered. This goes beyond a simple write operation as the in-progress work is permanently lost.

From the tool's definition Cancel a running pipeline job

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_pipeline_job 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 cancel_pipeline_job, this is the rule to start with:

cancel_pipeline_job Hidden

cancel_pipeline_job is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_pipeline_job"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every cancel_pipeline_job call is checked against it from then on.

FAQ

Questions about cancel_pipeline_job

What does the cancel_pipeline_job tool do? +

Cancel a running pipeline job. It is categorised as a Destructive tool in the Gitlab Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_pipeline_job? +

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

What risk level is cancel_pipeline_job? +

cancel_pipeline_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_pipeline_job? +

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

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

cancel_pipeline_job 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.

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP →delete_cron_job on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →