salesforce_create_lead
AI agents use salesforce_create_lead 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.
This tool creates new lead records in Salesforce, which is a reversible write operation. It modifies state by adding data but does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The medium severity reflects the moderate blast radius of creating spurious or incorrect lead records in a CRM system, though such records can be deleted or corrected.
From the tool's definition Tool name 'salesforce_create_lead' indicates creation of new lead records. Server description confirms 'CRUD actions' are supported.
Attacks that exploit this kind of access
salesforce_create_lead. 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 salesforce_create_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 Salesforce MCP Server. Nothing to install.
salesforce_create_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 salesforce_create_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 salesforce_create_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.
salesforce_create_lead is provided by the Salesforce MCP Server MCP server (sowmya-rapid/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 →