sf_delete_record
Deletes a single SObject record by record ID via the Salesforce REST API. The deletion is permanent and cannot be undone (the record goes to the Recycle Bin for objects that support it, from where it can be undeleted within 15 days). Provide the object API name and the 15 or 18 character record I...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-delete-record.md
What sf_delete_record does on Salesforce Metadata Mcp
AI agents call sf_delete_record to permanently remove resources in Salesforce Metadata Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why sf_delete_record is rated Critical
This tool irreversibly deletes data from Salesforce. Although Salesforce provides a 15-day recovery window via the Recycle Bin for supported objects, the primary action is permanent deletion that cannot be undone in normal operation. This is a clear destructive action with significant business impact if misused by an AI agent (e.g., deleting critical customer records, contracts, or financial data).
From the tool's definition Deletes a single SObject record by record ID via the Salesforce REST API. The deletion is permanent and cannot be undone (the record goes to the Recycle Bin for objects that support it, from where it can be undeleted within 15 days).
Attacks that exploit this kind of access
The rule that runs sf_delete_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_delete_record, this is the rule to start with:
sf_delete_record is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_delete_record call is checked against it from then on.
Questions about sf_delete_record
Deletes a single SObject record by record ID via the Salesforce REST API. The deletion is permanent and cannot be undone (the record goes to the Recycle Bin for objects that support it, from where it can be undeleted within 15 days). Provide the object API name and the 15 or 18 character record ID. For bulk deletions (100+ records), use sf_bulk_import_records with operation=. It is categorised as a Destructive tool in the Salesforce Metadata Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_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 Metadata Mcp. Nothing to install.
sf_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 sf_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 sf_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.
sf_delete_record is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
Across the catalogue