create_buyer_group
Create a buyer group for a company. Governed write: previews by default. A live write requires dryRun:false plus approved:true, a reason, and an idempotencyKey, and the connection must hold write:buyer-groups (connect_workspace with writeAccess:true).
This record as markdown: /tools/adrata-starfield-mcp/create-buyer-group.md
What create_buyer_group does on Starfield
AI agents use create_buyer_group 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 |
|---|---|---|---|
name | string | Yes | |
dryRun | boolean | — | Defaults to true. Returns a preview of the exact call instead of performing it. Set false to execute. |
reason | string | — | Required for a live write. Recorded as the audit reason (X-Adrata-Reason). |
approved | boolean | — | Required (true) for a live write. Records that the caller confirmed the mutation; it does not by itself grant scope. |
companyId | string | Yes | |
idempotencyKey | string | — | Required for a live write. Sent as Idempotency-Key so a retry cannot double-apply. |
Parameters from the server's own tool schema.
Why create_buyer_group is rated Medium
An AI agent can call create_buyer_group 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 create_buyer_group 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 create_buyer_group, this is the rule to start with:
create_buyer_group 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 create_buyer_group call is checked against it from then on.
Questions about create_buyer_group
Create a buyer group for a company. Governed write: previews by default. A live write requires dryRun:false plus approved:true, a reason, and an idempotencyKey, and the connection must hold write:buyer-groups (connect_workspace with writeAccess:true). 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.
create_buyer_group accepts 6 parameters: name, dryRun, reason, approved, companyId, idempotencyKey. Required: name, companyId. 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 create_buyer_group: 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.
create_buyer_group 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 create_buyer_group 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 create_buyer_group. 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.
create_buyer_group 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