pipedrive_convert_lead_to_deal
Convert a lead into a deal (Pipedrive v2). 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.
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 use pipedrive_convert_lead_to_deal to create or update resources in Pipedrive MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pipedrive MCP Server environment.
Why pipedrive_convert_lead_to_deal is rated Medium
This tool creates a new deal record by converting an existing lead, which is a reversible data modification operation (deals can typically be deleted or converted back in a CRM system). It does not permanently destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool description states it 'Convert[s] a lead into a deal' and 'returns the new deal ID', indicating creation of a new deal record in Pipedrive CRM.
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 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
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). 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. It is categorised as a Write tool in the Pipedrive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 (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.
This server
Across the catalogue