sf_bulk_import_records
Bulk imports records using the Salesforce Bulk API 2.0. Supports insert, upsert, update, and delete operations on large datasets (thousands to millions of records). Provide CSV data with a header row. For upsert, set externalIdField to the field used for matching. Polls until the job completes an...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-bulk-import-records.md
What sf_bulk_import_records does on Salesforce Metadata Mcp
AI agents use sf_bulk_import_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.
Why sf_bulk_import_records is rated Medium
This tool primarily creates and modifies data reversibly (insert, upsert, update operations on large datasets), which is the defining characteristic of Write category. Although delete operations are supported, they appear secondary to the main use cases. The scale (thousands to millions of records) and potential for widespread data modification elevate severity to high.
From the tool's definition Tool description explicitly states it "Supports insert, upsert, update, and delete operations on large datasets (thousands to millions of records)" using Salesforce Bulk API 2.0.
Attacks that exploit this kind of access
The rule that runs sf_bulk_import_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_import_records, this is the rule to start with:
sf_bulk_import_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_bulk_import_records call is checked against it from then on.
Questions about sf_bulk_import_records
Bulk imports records using the Salesforce Bulk API 2.0. Supports insert, upsert, update, and delete operations on large datasets (thousands to millions of records). Provide CSV data with a header row. For upsert, set externalIdField to the field used for matching. Polls until the job completes and returns success/failure counts. 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.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_bulk_import_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.
sf_bulk_import_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sf_bulk_import_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.
Set action: deny in the PolicyLayer policy for sf_bulk_import_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.
sf_bulk_import_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.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue