sf_bulk_delete_records

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-bulk-delete-records.md

WHAT IT DOES

What sf_bulk_delete_records does on Salesforce Metadata Mcp

AI agents call sf_bulk_delete_records 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.

RISK

Why sf_bulk_delete_records is rated Critical

This tool permanently removes records from Salesforce, an irreversible action. While Salesforce's Recycle Bin provides temporary recovery, the primary effect is deletion of data. The asynchronous bulk processing of multiple records amplifies the blast radius—a single invocation can eliminate hundreds or thousands of records at once.

From the tool's definition Tool description explicitly states "Deletes multiple records by ID" and "Use with caution — deleted records go to the Recycle Bin." The verb "deletes" combined with "irreversibly" removing data (even to Recycle Bin) fits the Destructive category definition.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_bulk_delete_records 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_bulk_delete_records, this is the rule to start with:

sf_bulk_delete_records Hidden

sf_bulk_delete_records is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sf_bulk_delete_records"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_bulk_delete_records call is checked against it from then on.

FAQ

Questions about sf_bulk_delete_records

What does the sf_bulk_delete_records tool do? +

Deletes multiple records by ID asynchronously using Salesforce Bulk API 2.0. Returns a job ID to track status. Use with caution — deleted records go to the Recycle Bin. objectApiName: Salesforce object API name ids: array of Salesforce record IDs to delete. 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.

How do I enforce a policy on sf_bulk_delete_records? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_bulk_delete_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 Metadata Mcp. Nothing to install.

What risk level is sf_bulk_delete_records? +

sf_bulk_delete_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 sf_bulk_delete_records? +

Yes. Add a rate_limit block to the sf_bulk_delete_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 sf_bulk_delete_records completely? +

Set action: deny in the PolicyLayer policy for sf_bulk_delete_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 sf_bulk_delete_records? +

sf_bulk_delete_records 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.

KEEP EXPLORING

More on Salesforce Metadata, and thousands of servers like it.

This server

All 213 Salesforce Metadata tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →