// MCP TOOL REFERENCE

salesforce_dml_records

ServerSalesforce MCP Server
CategoryDestructive

WHAT IT DOES

What salesforce_dml_records does on Salesforce MCP Server

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.

THE RISK

Critical Risk

Why salesforce_dml_records needs a policy

While this tool includes Write operations (insert, update, upsert), it also enables delete operations which irreversibly remove records and cannot be undone. According to the classification rules, Destructive is more severe than Write and should be assigned when a tool permits data deletion.

From the tool's definition The tool performs 'delete: Remove records (requires Id)' operations that irreversibly remove data from Salesforce.

Documented attack patterns abuse exactly the kind of access salesforce_dml_records gives an agent:

POLICY

How to control salesforce_dml_records

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:

policy.json

{
  "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.

Create a free account and register Salesforce MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Salesforce MCP Server tools

Execute salesforce_query_records Query records from any Salesforce object using SOQL, including relationship queries. Exam Write salesforce_manage_field Create new custom fields or modify existing fields on any Salesforce object: - Field Typ Write salesforce_manage_object Create new custom objects or modify existing ones in Salesforce: - Create: New custom ob Read salesforce_describe_object Get detailed schema metadata including all fields, relationships, and field properties of Read salesforce_search_objects Search for Salesforce standard and custom objects by name pattern. Examples:

All 6 Salesforce MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Salesforce MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about salesforce_dml_records

What does the salesforce_dml_records tool do? +

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.

How do I enforce a policy on salesforce_dml_records? +

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.

What risk level is salesforce_dml_records? +

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.

Can I rate-limit salesforce_dml_records? +

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.

How do I block salesforce_dml_records completely? +

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.

What MCP server provides salesforce_dml_records? +

salesforce_dml_records is provided by the Salesforce MCP Server MCP server (surajadsul/mcp-server-salesforce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Salesforce MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

6 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.