Perform record-level data operations: insert, update, delete, or upsert. Operates on one object type per call; pass an array of records.
AI agents call salesforce_dml_records to permanently remove resources in Salesforce — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the tool can also insert, update, and upsert (reversible Write operations), it includes delete functionality, which is irreversible and cannot be undone. Per the classification rules, when a tool spans categories, the most severe applies. Destructive supersedes Write.
From the tool's definition Tool description states it performs "insert, update, delete, or upsert" operations. The inclusion of "delete" makes this destructive—it irreversibly removes data. The description explicitly lists delete as a capability.
Attacks that exploit this kind of access
Perform record-level data operations: insert, update, delete, or upsert. Operates on one object type per call; pass an array of records. It is categorised as a Destructive tool in the Salesforce MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Salesforce MCP server in PolicyLayer and add a rule for salesforce_dml_records: 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. Nothing to install.
salesforce_dml_records is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the salesforce_dml_records 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_dml_records. 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_dml_records is provided by the Salesforce MCP server (wyre-technology/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 →