remove_list_target_usages

Remove all usages of a list target

Server AdButler adbutler/mcp-server
Category Destructive
Risk class Critical
Parameters 11 required

What remove_list_target_usages does on AdButler

AI agents call remove_list_target_usages 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.

ParameterTypeRequiredDescription
id number Yes List target ID

Parameters from the server's own tool schema.

Why remove_list_target_usages needs a policy

The verb 'remove' combined with 'all usages' describes a bulk deletion operation that cannot be undone. This affects advertising campaign targeting data, which once deleted cannot be recovered. While not a direct data destruction like 'delete_list', removing all usages of a targeting list is a destructive action that eliminates advertising configurations.

From the tool's definition Tool name 'remove_list_target_usages' and description 'Remove all usages of a list target' indicate irreversible deletion of targeting configurations.

Questions about remove_list_target_usages

What does the remove_list_target_usages tool do? +

Remove all usages of a list target. 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.

What parameters does remove_list_target_usages accept? +

remove_list_target_usages accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remove_list_target_usages? +

Register the AdButler MCP server in PolicyLayer and add a rule for remove_list_target_usages: 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.

What risk level is remove_list_target_usages? +

remove_list_target_usages is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_list_target_usages? +

Yes. Add a rate_limit block to the remove_list_target_usages 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.

How do I block remove_list_target_usages completely? +

Set action: deny in the PolicyLayer policy for remove_list_target_usages. 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.

What MCP server provides remove_list_target_usages? +

remove_list_target_usages 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.