AI agents use convert_lead to create or update resources in EspoCRM-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EspoCRM-MCP environment.
This tool creates new records (contact, account, opportunity) from a lead. While the operation is somewhat complex, it remains reversible through deletion or modification of the created records. The high severity reflects that careless or malicious conversion of many leads could create large volumes of unwanted customer records in the CRM, impacting data quality and downstream processes.
From the tool's definition Tool description states 'Convert a lead to contact, account, and/or opportunity' - this creates new entities (contact, account, opportunity records) from an existing lead, which is a data transformation that creates or modifies data reversibly.
Documented attack patterns abuse exactly the kind of access convert_lead gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EspoCRM-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_lead:
{
"version": "1",
"default": "deny",
"tools": {
"convert_lead": {
"limits": [
{
"counter": "convert_lead_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Convert a lead to contact, account, and/or opportunity. It is categorised as a Write tool in the EspoCRM-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EspoCRM- 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 EspoCRM-MCP. 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 EspoCRM- MCP server (zaphod-black/espomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 EspoCRM-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
46 EspoCRM-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.