Deletes a record
AI agents call delete_record to permanently remove resources in MCP Salesforce Connector — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_record tool permanently removes records from Salesforce and cannot be undone. While individual record deletion has a narrower blast radius than bulk operations (bulk_delete_records), it still qualifies as Destructive rather than Write because deletion is inherently irreversible.
From the tool's definition Tool name 'delete_record' and description 'Deletes a record' indicate permanent removal of data from Salesforce. This is an irreversible operation that destroys data.
Attacks that exploit this kind of access
Deletes a record. It is categorised as a Destructive tool in the MCP Salesforce Connector MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Salesforce Connector 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 MCP Salesforce Connector. 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 MCP Salesforce Connector MCP server (smn2gnt/mcp-salesforce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.