Upsert records using external ID with auto-bulk switching
AI agents use upsert-record 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.
Upsert is a reversible write operation that creates new records or updates existing ones based on an external ID match. While data can be recovered via Salesforce's recycle bin or backups, the operation itself modifies business-critical CRM data.
From the tool's definition Upsert records using external ID with auto-bulk switching — upsert is a combined create-or-update operation that modifies data in Salesforce. The description explicitly states it performs record upsert operations.
Documented attack patterns abuse exactly the kind of access upsert-record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upsert-record:
{
"version": "1",
"default": "deny",
"tools": {
"upsert-record": {
"limits": [
{
"counter": "upsert-record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upsert-record 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.
Upsert records using external ID with auto-bulk switching. 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 upsert-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 Salesforce MCP Server. Nothing to install.
upsert-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 upsert-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 upsert-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.
upsert-record is provided by the Salesforce MCP Server MCP server (jaworjar95/salesforce-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.