Delete records by ID(s) with auto-bulk switching
AI agents call delete-record 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.
This tool irreversibly deletes data records from Salesforce by ID. Deletion cannot be undone without backup restoration or manual recovery processes. The ability to delete multiple records in bulk amplifies the blast radius. An AI agent with unconstrained access could delete critical business records (accounts, opportunities, contacts, transactions) causing significant data loss and business disruption.
From the tool's definition Tool name 'delete-record' explicitly indicates deletion functionality. Description states 'Delete records by ID(s)' which performs irreversible removal of data from Salesforce. The 'auto-bulk switching' suggests it can operate at scale.
Documented attack patterns abuse exactly the kind of access delete-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 delete-record:
{
"version": "1",
"default": "deny",
"hide": [
"delete-record"
]
} delete-record 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.
Delete records by ID(s) with auto-bulk switching. 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 delete-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.
delete-record 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 delete-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 delete-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.
delete-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.