convert_lead_to_opportunity
AI agents use convert_lead_to_opportunity to create or update resources in Salesforce MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce MCP Server environment.
Converting a lead to an opportunity in Salesforce is a significant write operation that creates new records (opportunity, contact, account) and changes the lead's status to converted. It is reversible in principle (records can be deleted afterward) but has broad side effects across multiple objects. Classified as Write rather than Execute because it is a well-defined CRM workflow action, not arbitrary code execution.
From the tool's definition Tool name 'convert_lead_to_opportunity' — description is empty and uninformative.
Attacks that exploit this kind of access
convert_lead_to_opportunity. It is categorised as a Write tool in the Salesforce MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for convert_lead_to_opportunity: 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 Salesforce MCP Server. Nothing to install.
convert_lead_to_opportunity 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_to_opportunity 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_to_opportunity. 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_to_opportunity is provided by the Salesforce MCP Server MCP server (obot-platform/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →