Remove values from a list attribute for a user
AI agents call remove_user_list_attribute_values 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 |
|---|---|---|---|
values | array | — | Values to remove |
user_id | string | Yes | User ID |
user_db_id | number | Yes | User database ID |
list_attribute_name | string | Yes | List attribute name |
Parameters from the server's own tool schema.
The tool removes (deletes) specific values from a user's list attribute. This is a destructive operation as removed attribute values are unlikely to be recoverable without explicit audit trails or backups. Combined with sibling tools like 'archive_advertiser' and 'bulk_upload_add_data_list', this server pattern suggests permanent data modification.
From the tool's definition 'Remove values from a list attribute for a user' — removing values is an irreversible deletion of user attribute data
Attacks that exploit this kind of access
Remove values from a list attribute for a user. 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.
remove_user_list_attribute_values accepts 4 parameters: values, user_id, user_db_id, list_attribute_name. Required: user_id, user_db_id, list_attribute_name. 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 remove_user_list_attribute_values: 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.
remove_user_list_attribute_values 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_user_list_attribute_values 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_user_list_attribute_values. 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_user_list_attribute_values 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →