Create a new Salesforce record
AI agents use create_record to create or update resources in MCP Salesforce Lite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Salesforce Lite environment.
This tool creates new data in Salesforce CRM (Accounts, Contacts, Opportunities, etc.) in a reversible manner. It does not execute code, delete data, or move money. The severity is medium because while the action is reversible, unauthorized record creation in a CRM system could result in data pollution, duplicate entries, or operational confusion, affecting business processes and data integrity.
From the tool's definition Tool description states 'Create a new Salesforce record' and is listed alongside CRUD operations. The server explicitly supports 'CRUD operations' including create functionality.
Attacks that exploit this kind of access
Create a new Salesforce record. It is categorised as a Write tool in the MCP Salesforce Lite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Salesforce Lite MCP server in PolicyLayer and add a rule for create_record: 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 MCP Salesforce Lite. Nothing to install.
create_record 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 create_record 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 create_record. 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.
create_record is provided by the MCP Salesforce Lite MCP server (luvl/mcp-salesforce-lite). 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 →