Delete a publisher
AI agents call delete_publisher 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 | Publisher ID |
Parameters from the server's own tool schema.
This tool irreversibly deletes publisher records from the AdButler ad management system. Deletion cannot be undone without database restoration. Even though the blast radius is limited to publisher data (not system-wide), the permanent nature of the operation and its potential to disrupt advertising operations (loss of publisher configuration, historical data, associated campaigns) justifies 'Destructive'…
From the tool's definition Tool name 'delete_publisher' combined with description 'Delete a publisher' explicitly states irreversible deletion of a publisher entity.
Attacks that exploit this kind of access
Delete a publisher. 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_publisher 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_publisher: 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_publisher 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_publisher 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_publisher. 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_publisher 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 →