sf_bulk_update_records

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee 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-update-records.md

WHAT IT DOES

What sf_bulk_update_records does on Salesforce Metadata Mcp

AI agents use sf_bulk_update_records to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.

RISK

Why sf_bulk_update_records is rated Medium

This tool modifies existing data (Update) but does not delete or destroy it irreversibly, placing it in the Write category. However, the severity is high rather than medium because: (1) it operates on multiple records at scale via Bulk API, (2) updates are asynchronous and may affect business-critical data, (3) improper use could corrupt or overwrite significant portions of an organization's Salesforce database…

From the tool's definition Tool description states 'Updates multiple records' which is a write operation. The Bulk API 2.0 is specifically designed for mass modification of data in Salesforce, operating asynchronously on multiple records simultaneously.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sf_bulk_update_records Rate-limited

sf_bulk_update_records stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_bulk_update_records": {
      "limits": [
        {
          "counter": "sf_bulk_update_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_update_records call is checked against it from then on.

FAQ

Questions about sf_bulk_update_records

What does the sf_bulk_update_records tool do? +

Updates multiple records of the same object type asynchronously using Salesforce Bulk API 2.0. Each record must include its Salesforce Id field. Returns a job ID to track status. objectApiName: Salesforce object API name records: array of records — each must include. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sf_bulk_update_records? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_bulk_update_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_update_records? +

sf_bulk_update_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sf_bulk_update_records? +

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

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

sf_bulk_update_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 →

Across the catalogue

sms_send_bulk on Twilio SMS MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →