pipedrive_convert_deal_to_lead

SERVERPipedrive MCP Server SOURCEckalima/pipedrive-mcp-server

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/ckalima-pipedrive-mcp-server/pipedrive-convert-deal-to-lead.md

WHAT IT DOES

What pipedrive_convert_deal_to_lead does on Pipedrive MCP Server

AI agents call pipedrive_convert_deal_to_lead 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.

RISK

Why pipedrive_convert_deal_to_lead is rated Critical

The tool explicitly states it is destructive and that the source deal is deleted upon successful conversion. Deletion of CRM deal data is irreversible, placing this firmly in the Destructive category. The high severity reflects the blast radius: losing a deal record in a CRM pipeline can have significant business consequences and cannot be undone.

From the tool's definition DESTRUCTIVE: a successful conversion marks the source deal as deleted

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pipedrive_convert_deal_to_lead Hidden

pipedrive_convert_deal_to_lead 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": [
    "pipedrive_convert_deal_to_lead"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_convert_deal_to_lead call is checked against it from then on.

FAQ

Questions about pipedrive_convert_deal_to_lead

What does the pipedrive_convert_deal_to_lead tool do? +

Convert a deal to a lead (async job). DESTRUCTIVE: a successful conversion marks the source deal as deleted. Returns a conversion_id; the conversion runs asynchronously, so you MUST poll pipedrive_get_deal_conversion_status with the conversion_id until a terminal status. 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.

How do I enforce a policy on pipedrive_convert_deal_to_lead? +

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

What risk level is pipedrive_convert_deal_to_lead? +

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

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

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

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

KEEP EXPLORING

More on Pipedrive MCP Server, and thousands of servers like it.

This server

All 155 Pipedrive MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →