delete_pipeline_tool

Delete a CI/CD pipeline and all its jobs permanently.

Server MCP Gitlab mcp-gitlab-crunchtools
Category Destructive
Risk class Critical
Parameters 00 required

What delete_pipeline_tool does on MCP Gitlab

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

Why delete_pipeline_tool needs a policy

The tool irreversibly deletes CI/CD pipelines and associated jobs. The verb 'Delete' combined with 'permanently' and the absence of any undo mechanism places this in the Destructive category.

From the tool's definition Delete a CI/CD pipeline and all its jobs permanently.

Questions about delete_pipeline_tool

What does the delete_pipeline_tool tool do? +

Delete a CI/CD pipeline and all its jobs permanently. It is categorised as a Destructive tool in the MCP Gitlab 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 delete_pipeline_tool? +

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

delete_pipeline_tool 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 delete_pipeline_tool? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.