remove_buyer_group_member
Remove one person from a buyer group. Does NOT delete the underlying person record. To remove the whole room, use delete_buyer_group instead — it cascades. Governed write: previews by default. A live write requires dryRun:false plus approved:true, a reason, and an idempotencyKey, and the connecti...
This record as markdown: /tools/adrata-starfield-mcp/remove-buyer-group-member.md
What remove_buyer_group_member does on Starfield
AI agents call remove_buyer_group_member to permanently remove resources in Starfield, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
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. |
memberId | string | Yes | |
buyerGroupId | 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 remove_buyer_group_member is rated Critical
An AI agent that decides to call remove_buyer_group_member doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Starfield is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remove_buyer_group_member 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 remove_buyer_group_member, this is the rule to start with:
remove_buyer_group_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every remove_buyer_group_member call is checked against it from then on.
Questions about remove_buyer_group_member
Remove one person from a buyer group. Does NOT delete the underlying person record. To remove the whole room, use delete_buyer_group instead — it cascades. 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 Destructive tool in the Starfield MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_buyer_group_member accepts 6 parameters: dryRun, reason, approved, memberId, buyerGroupId, idempotencyKey. Required: memberId, buyerGroupId. 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 remove_buyer_group_member: 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.
remove_buyer_group_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_buyer_group_member 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 remove_buyer_group_member. 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.
remove_buyer_group_member 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.
Across the catalogue