bulk_upload_remove_data_list
Bulk remove entries from a data list
This record as markdown: /tools/adbutler/bulk-upload-remove-data-list.md
What bulk_upload_remove_data_list does on AdButler
AI agents call bulk_upload_remove_data_list to permanently remove resources in AdButler, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Data list ID |
data | string | — | CSV data to remove |
Parameters from the server's own tool schema.
Why bulk_upload_remove_data_list is rated Critical
The tool bulk removes entries from a data list, which constitutes irreversible deletion. The 'bulk' nature amplifies the blast radius significantly, as an AI agent could accidentally remove large numbers of entries that may not be recoverable, warranting a high severity rating.
From the tool's definition 'Bulk remove entries from a data list' — bulk removal of data entries is irreversible deletion at scale
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_upload_remove_data_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_upload_remove_data_list, this is the rule to start with:
bulk_upload_remove_data_list 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 AdButler, apply this rule, and every bulk_upload_remove_data_list call is checked against it from then on.
Questions about bulk_upload_remove_data_list
Bulk remove entries from a data list. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
bulk_upload_remove_data_list accepts 2 parameters: id, data. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for bulk_upload_remove_data_list: 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 AdButler. Nothing to install.
bulk_upload_remove_data_list 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_upload_remove_data_list 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_upload_remove_data_list. 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_upload_remove_data_list is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
Across the catalogue