Update single or multiple records with auto-bulk switching
AI agents use update-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.
This tool creates or modifies data reversibly—the hallmark of Write category. It does not delete data (which would be Destructive) or move money (Financial). However, severity is high because: (1) it operates on Salesforce records which often contain sensitive customer/business data, (2) bulk update capability means a single misuse could affect many records, (3) updates are generally reversible but can still cause…
From the tool's definition Tool name 'update-record' explicitly describes modifying records. Description confirms it 'Update[s] single or multiple records'. The 'auto-bulk switching' capability indicates it can modify at scale.
Documented attack patterns abuse exactly the kind of access update-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 update-record:
{
"version": "1",
"default": "deny",
"tools": {
"update-record": {
"limits": [
{
"counter": "update-record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-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.
Update single or multiple records 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 update-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.
update-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 update-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 update-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.
update-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.