bulk_delete_buyer_groups
Soft-delete up to 50 buyer groups in ONE call, each cascading to its members. Use this instead of looping delete_buyer_group when cleaning many rooms out of a workspace.
This record as markdown: /tools/adrata-adrata-mcp/bulk-delete-buyer-groups.md
What bulk_delete_buyer_groups does on Adrata
AI agents call bulk_delete_buyer_groups to permanently remove resources in Adrata, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bulk_delete_buyer_groups is rated Critical
An AI agent that decides to call bulk_delete_buyer_groups doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Adrata is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_delete_buyer_groups safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_delete_buyer_groups, this is the rule to start with:
bulk_delete_buyer_groups 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 Adrata, apply this rule, and every bulk_delete_buyer_groups call is checked against it from then on.
Questions about bulk_delete_buyer_groups
Soft-delete up to 50 buyer groups in ONE call, each cascading to its members. Use this instead of looping delete_buyer_group when cleaning many rooms out of a workspace. It is categorised as a Destructive tool in the Adrata MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Adrata MCP server in PolicyLayer and add a rule for bulk_delete_buyer_groups: 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 Adrata. Nothing to install.
bulk_delete_buyer_groups 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 bulk_delete_buyer_groups 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_delete_buyer_groups. 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_delete_buyer_groups is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
Across the catalogue