salesforce_create_record
AI agents use salesforce_create_record to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
The tool creates new records in Salesforce, a major CRM platform. This is a reversible write operation with potential business impact (new contacts, leads, opportunities, or accounts could be created), justifying 'high' severity. Confidence is 0.85 rather than higher due to the empty description, which prevents confirmation of record type or any guardrails.
From the tool's definition Tool name 'salesforce_create_record' explicitly indicates creation of a record in Salesforce. The 'create' verb denotes a write operation that modifies data. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
salesforce_create_record. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for salesforce_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 Integrations MCP. Nothing to install.
salesforce_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 salesforce_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 salesforce_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.
salesforce_create_record is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →