pipedrive_delete_pipeline
Delete a pipeline. Marks the pipeline as deleted. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-delete-pipeline.md
What pipedrive_delete_pipeline does on Pipedrive MCP Server
AI agents call pipedrive_delete_pipeline to permanently remove resources in Pipedrive MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pipedrive_delete_pipeline is rated Critical
This tool permanently deletes pipelines in a CRM system, which cannot be undone. Deletion of pipeline data could impact business operations, sales tracking, and workflow management. While not directly financial, the high blast radius and irreversibility place this in the Destructive category rather than Write.
From the tool's definition 'Delete a pipeline. Marks the pipeline as deleted.' - The tool explicitly performs deletion of a pipeline, which is an irreversible operation.
Attacks that exploit this kind of access
The rule that runs pipedrive_delete_pipeline safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pipedrive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_delete_pipeline, this is the rule to start with:
pipedrive_delete_pipeline is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_delete_pipeline call is checked against it from then on.
Questions about pipedrive_delete_pipeline
Delete a pipeline. Marks the pipeline as deleted. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true). It is categorised as a Destructive tool in the Pipedrive MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for pipedrive_delete_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 Pipedrive MCP Server. Nothing to install.
pipedrive_delete_pipeline is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pipedrive_delete_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.
Set action: deny in the PolicyLayer policy for pipedrive_delete_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.
pipedrive_delete_pipeline is provided by the Pipedrive MCP Server MCP server (ckalima/pipedrive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pipedrive MCP Server, and thousands of servers like it.
Across the catalogue