delete_placement
Delete a placement (remove an ad item from a zone)
This record as markdown: /tools/adbutler/delete-placement.md
What delete_placement does on AdButler
AI agents call delete_placement 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 | Placement ID |
Parameters from the server's own tool schema.
Why delete_placement is rated Critical
This tool permanently removes an ad placement configuration from a zone, which cannot be undone without recreation. In the AdButler ad management context, deleting a placement disrupts active advertising operations and campaign delivery.
From the tool's definition Tool name is 'delete_placement' and description states 'Delete a placement (remove an ad item from a zone)' — the verb 'delete' and the irreversible removal of an ad placement from operational zones indicates destructive action.
Attacks that exploit this kind of access
The rule that runs delete_placement 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 delete_placement, this is the rule to start with:
delete_placement 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 delete_placement call is checked against it from then on.
Questions about delete_placement
Delete a placement (remove an ad item from a zone). 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_placement accepts 1 parameter: id. 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 delete_placement: 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_placement 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_placement 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_placement. 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_placement 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