delete_zone_ortb_native_ad
Delete an ORTB native ad from a standard zone
This record as markdown: /tools/adbutler/delete-zone-ortb-native-ad.md
What delete_zone_ortb_native_ad does on AdButler
AI agents call delete_zone_ortb_native_ad 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 | ORTB native ad ID |
zone_id | number | Yes | Standard zone ID |
Parameters from the server's own tool schema.
Why delete_zone_ortb_native_ad is rated Critical
This tool performs an irreversible deletion of an ORTB native ad configuration. While the blast radius is scoped to a single ad entity rather than an entire campaign or publisher, deletion cannot be undone and represents permanent data loss. This satisfies the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Tool name contains 'delete' and description states 'Delete an ORTB native ad from a standard zone'. The operation removes ad configuration data from a zone irreversibly.
Attacks that exploit this kind of access
The rule that runs delete_zone_ortb_native_ad 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_zone_ortb_native_ad, this is the rule to start with:
delete_zone_ortb_native_ad 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_zone_ortb_native_ad call is checked against it from then on.
Questions about delete_zone_ortb_native_ad
Delete an ORTB native ad from a standard 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_zone_ortb_native_ad accepts 2 parameters: id, zone_id. Required: id, zone_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_zone_ortb_native_ad: 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_zone_ortb_native_ad 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_zone_ortb_native_ad 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_zone_ortb_native_ad. 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_zone_ortb_native_ad 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