export_data
Export records as JSON or CSV with filters. Supports companies, people, opportunities, actions, and notes. Includes custom fields. Enterprise only.
This record as markdown: /tools/adrata-starfield-mcp/export-data.md
What export_data does on Starfield
AI agents use export_data 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 |
|---|---|---|---|
limit | number | — | Max records to export (default 100, max 1000) |
entity | string | Yes | Record type to export |
fields | array | — | Specific fields to include (default: all) |
format | string | — | Output format (default: json) |
filters | object | — | Optional filters to narrow the export |
Parameters from the server's own tool schema.
Why export_data is rated Medium
An AI agent can call export_data 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 signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs export_data 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 export_data, this is the rule to start with:
export_data 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 export_data call is checked against it from then on.
Questions about export_data
Export records as JSON or CSV with filters. Supports companies, people, opportunities, actions, and notes. Includes custom fields. 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.
export_data accepts 5 parameters: limit, entity, fields, format, filters. Required: entity. 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 export_data: 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.
export_data 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 export_data 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 export_data. 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.
export_data 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