Perform data manipulation operations on Salesforce records: - insert: Create new records - update: Modify existing records (requires Id) - delete: Remove records (requires Id) - upsert: Insert or update based on external ID field Examples: Insert new Accounts, Update Case status, Delete old recor...
AI agents call salesforce_dml_records to permanently remove resources in Salesforce MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While this tool includes reversible write operations (insert, update, upsert), it also includes the delete operation which irreversibly removes records from Salesforce. Per the classification rules, when a tool spans multiple categories, the most severe applies. Destructive (irreversible deletion) is more severe than Write.
From the tool's definition Tool description explicitly includes 'delete: Remove records' and 'Perform data manipulation operations' with operations spanning insert, update, delete, and upsert on Salesforce records.
Documented attack patterns abuse exactly the kind of access salesforce_dml_records 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 salesforce_dml_records:
{
"version": "1",
"default": "deny",
"hide": [
"salesforce_dml_records"
]
}salesforce_dml_records disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Perform data manipulation operations on Salesforce records: - insert: Create new records - update: Modify existing records (requires Id) - delete: Remove records (requires Id) - upsert: Insert or update based on external ID field Examples: Insert new Accounts, Update Case status, Delete old records, Upsert based on custom external ID. It is categorised as a Destructive tool in the Salesforce MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Salesforce MCP Server 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 MCP Server. 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 MCP server (tsmztech/mcp-server-salesforce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Salesforce MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Salesforce MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.