Delete a user attribute from a user database
AI agents call delete_user_attribute 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 | User attribute ID |
user_db_id | number | Yes | User database ID |
Parameters from the server's own tool schema.
This tool permanently removes user attribute data from a database with no undo mechanism implied. Deletion of user database records is irreversible and qualifies as Destructive rather than Write (which is reversible). In an ad-serving context, loss of user attribute data could break targeting logic or user records.
From the tool's definition Tool name is 'delete_user_attribute' and description states 'Delete a user attribute from a user database'. The verb 'delete' combined with permanent removal of data attributes constitutes an irreversible destructive operation.
Attacks that exploit this kind of access
Delete a user attribute from a user database. 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.
delete_user_attribute accepts 2 parameters: id, user_db_id. Required: id, user_db_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 delete_user_attribute: 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.
delete_user_attribute 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 delete_user_attribute 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 delete_user_attribute. 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.
delete_user_attribute 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 →