pipedrive_convert_lead_to_deal
Convert a lead into a deal (Pipedrive v2). DESTRUCTIVE: a successful conversion marks the source lead as deleted. The conversion runs asynchronously; this tool polls until it completes (typically under 5s) and returns the new deal ID. If it is still running after ~30s, it returns the conversion_i...
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-convert-lead-to-deal.md
What pipedrive_convert_lead_to_deal does on Pipedrive MCP Server
AI agents call pipedrive_convert_lead_to_deal 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_convert_lead_to_deal is rated Critical
The tool explicitly states it is destructive because converting a lead to a deal permanently deletes the source lead. This is an irreversible action — the original lead record is marked as deleted upon successful conversion. Despite also creating a new deal (a Write operation), the most severe applicable category is Destructive due to the irreversible deletion of the lead.
From the tool's definition DESTRUCTIVE: a successful conversion marks the source lead as deleted
Attacks that exploit this kind of access
The rule that runs pipedrive_convert_lead_to_deal 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_convert_lead_to_deal, this is the rule to start with:
pipedrive_convert_lead_to_deal 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_convert_lead_to_deal call is checked against it from then on.
Questions about pipedrive_convert_lead_to_deal
Convert a lead into a deal (Pipedrive v2). DESTRUCTIVE: a successful conversion marks the source lead as deleted. The conversion runs asynchronously; this tool polls until it completes (typically under 5s) and returns the new deal ID. If it is still running after ~30s, it returns the conversion_id and status for manual follow-up. 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_convert_lead_to_deal: 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_convert_lead_to_deal 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_convert_lead_to_deal 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_convert_lead_to_deal. 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_convert_lead_to_deal is provided by the Pipedrive MCP Server MCP server (https://github.com/ckalima/pipedrive-mcp-server/releases/download/v2.7.0/pipedrive-mcp-server-2.7.0.mcpb). 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