convert_lead
Convert an account: qualify its open lead (creating one if needed) and link exactly one pipeline deal. Also promotes lifeStage lead -> active. Safe to repeat — a second call lands on the same lead and deal. Works on accounts that are already active.
This record as markdown: /tools/io-favcrm-favcrm/convert-lead.md
What convert_lead does on FavCRM
AI agents use convert_lead to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
dealName | string | — | Optional deal name |
accountId | string | Yes | Lead account ID |
dealStage | string | — | Optional initial deal stage ("lead" is an alias of "discovery") |
lifeStage | string | — | Lifecycle after convert (default active) |
createDeal | boolean | — | Deprecated and ignored — a convert always links a deal |
dealAmount | number | — | Optional deal amount |
dealClosingDate | string | — | Optional deal close date |
Parameters from the server's own tool schema.
Why convert_lead is rated Medium
An AI agent can call convert_lead faster than any human can review: one bad instruction and it creates or modifies resources in FavCRM by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs convert_lead safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_lead, this is the rule to start with:
convert_lead 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 FavCRM, apply this rule, and every convert_lead call is checked against it from then on.
Questions about convert_lead
Convert an account: qualify its open lead (creating one if needed) and link exactly one pipeline deal. Also promotes lifeStage lead -> active. Safe to repeat — a second call lands on the same lead and deal. Works on accounts that are already active. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
convert_lead accepts 7 parameters: dealName, accountId, dealStage, lifeStage, createDeal, dealAmount, dealClosingDate. Required: accountId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for convert_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 FavCRM. Nothing to install.
convert_lead 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 convert_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.
Set action: deny in the PolicyLayer policy for convert_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.
convert_lead is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue