import_external_companies
Import selected external catalog companies into the workspace through Adrata bulk import, then use check_batch_import_status and rank_companies_by_icp for best-fit ordering.
This record as markdown: /tools/adrata-starfield-mcp/import-external-companies.md
What import_external_companies does on Starfield
AI agents use import_external_companies 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 |
|---|---|---|---|
ids | array | Yes | Adrata internal external_source_companies ids from list_external_companies |
dryRun | boolean | — | |
reason | string | — | |
approved | boolean | — |
Parameters from the server's own tool schema.
Why import_external_companies is rated Medium
An AI agent can call import_external_companies 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.
Attacks that exploit this kind of access
The rule that runs import_external_companies 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 import_external_companies, this is the rule to start with:
import_external_companies 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 import_external_companies call is checked against it from then on.
Questions about import_external_companies
Import selected external catalog companies into the workspace through Adrata bulk import, then use check_batch_import_status and rank_companies_by_icp for best-fit ordering. 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.
import_external_companies accepts 4 parameters: ids, dryRun, reason, approved. Required: ids. 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 import_external_companies: 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.
import_external_companies 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 import_external_companies 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 import_external_companies. 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.
import_external_companies 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