archive_zone
Archive a standard zone (soft-delete, can be restored later)
This record as markdown: /tools/adbutler/archive-zone.md
What archive_zone does on AdButler
AI agents use archive_zone to create or update resources in AdButler, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Zone ID |
Parameters from the server's own tool schema.
Why archive_zone is rated Medium
Archiving is a Write operation because it modifies data state reversibly. Although it removes a zone from active use, the description explicitly indicates it can be restored, distinguishing it from Destructive (permanent deletion). The severity is medium because archiving a zone affects advertising campaigns and operations, but the reversible nature prevents it from being high/critical.
From the tool's definition Tool name is 'archive_zone' and description explicitly states 'soft-delete, can be restored later.' This is a reversible modification operation—archiving is not permanent deletion but creates a changed state that can be undone.
Attacks that exploit this kind of access
The rule that runs archive_zone 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 archive_zone, this is the rule to start with:
archive_zone stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every archive_zone call is checked against it from then on.
Questions about archive_zone
Archive a standard zone (soft-delete, can be restored later). It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
archive_zone 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 archive_zone: 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.
archive_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the archive_zone 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 archive_zone. 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.
archive_zone 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.
This server
Across the catalogue