bulk_import
Import records in bulk from CSV data. Creates companies, people, or opportunities from structured CSV input. Each row becomes a record. Custom fields are supported via column names prefixed with "cf_" (e.g., cf_industry_segment). Returns created record IDs and any errors. Enterprise only.
This record as markdown: /tools/adrata-starfield-mcp/bulk-import.md
What bulk_import does on Starfield
AI agents use bulk_import to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
dryRun | boolean | — | If true, validate data without creating records (default: false) |
entity | string | Yes | Record type to import |
csvData | string | Yes | CSV string with headers in first row. Standard columns map to entity fields, cf_* columns map to customFields. |
skipDuplicates | boolean | — | If true, skip records that match existing records by email/domain (default: true) |
Parameters from the server's own tool schema.
Why bulk_import is rated Medium
An AI agent can call bulk_import faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_import safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_import, this is the rule to start with:
bulk_import 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 Starfield, apply this rule, and every bulk_import call is checked against it from then on.
Questions about bulk_import
Import records in bulk from CSV data. Creates companies, people, or opportunities from structured CSV input. Each row becomes a record. Custom fields are supported via column names prefixed with "cf_" (e.g., cf_industry_segment). Returns created record IDs and any errors. Enterprise only. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
bulk_import accepts 4 parameters: dryRun, entity, csvData, skipDuplicates. Required: entity, csvData. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for bulk_import: 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 Starfield. Nothing to install.
bulk_import 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 bulk_import 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 bulk_import. 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.
bulk_import is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue