sf_bulk_insert_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-insert-records.md

WHAT IT DOES

What sf_bulk_insert_records does on Salesforce Metadata Mcp

AI agents use sf_bulk_insert_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_insert_records is rated Medium

This tool creates new records (insert) or modifies existing ones (upsert) in Salesforce, which is a reversible write operation. The bulk nature and async processing increase impact potential compared to single-record writes, justifying 'medium' severity rather than 'low'. It does not delete data, execute arbitrary code, or involve financial transactions, so it does not warrant higher severity categories.

From the tool's definition Inserts multiple records of the same object type asynchronously using Salesforce Bulk API 2.0. Parameters include 'records: array of record objects with field:value pairs' and optional upsert functionality via 'externalIdField'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sf_bulk_insert_records Rate-limited

sf_bulk_insert_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_insert_records": {
      "limits": [
        {
          "counter": "sf_bulk_insert_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_insert_records call is checked against it from then on.

FAQ

Questions about sf_bulk_insert_records

What does the sf_bulk_insert_records tool do? +

Inserts multiple records of the same object type asynchronously using Salesforce Bulk API 2.0. More efficient than individual REST calls for large volumes. Returns a job ID to track status. objectApiName: Salesforce object API name records: array of record objects with field:value pairs externalIdField: if provided, performs an upsert on this external ID field instead of insert. 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_insert_records? +

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

sf_bulk_insert_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_insert_records? +

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

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

sf_bulk_insert_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 → The MCP Attack Database →

Guides

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