archive_zone · AdButler MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	Zone ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why archive_zone needs a policy

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

Recommended rule Ready

Verdict

archive_zone Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_zone": {
      "limits": [
        {
          "counter": "archive_zone_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AdButler, so you can run agents against it safely.

FAQ

Questions about archive_zone

What does the archive_zone tool do? +

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.

What parameters does archive_zone accept? +

archive_zone 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 archive_zone? +

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.

What risk level is archive_zone? +

archive_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit archive_zone? +

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.

How do I block archive_zone completely? +

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.

What MCP server provides archive_zone? +

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.