archive_campaign · AdButler MCP: Risk & Policy

WHAT IT DOES

What archive_campaign does on AdButler

AI agents use archive_campaign 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	Campaign ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why archive_campaign needs a policy

Archiving is a Write operation because it modifies campaign state reversibly—the campaign is hidden/disabled but not permanently deleted and can be restored. While it changes data, the reversibility and lack of permanent destruction distinguish it from Destructive. The blast radius is medium: archiving an active campaign could disrupt advertising operations, but restoration is possible.

From the tool's definition Tool name 'archive_campaign' and description 'soft-delete, can be restored later' indicate a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_campaign Rate-limited

archive_campaign 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_campaign": {
      "limits": [
        {
          "counter": "archive_campaign_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_campaign

What does the archive_campaign tool do? +

Archive a standard campaign (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_campaign accept? +

archive_campaign 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_campaign? +

Register the AdButler MCP server in PolicyLayer and add a rule for archive_campaign: 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_campaign? +

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

Can I rate-limit archive_campaign? +

Yes. Add a rate_limit block to the archive_campaign 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_campaign completely? +

Set action: deny in the PolicyLayer policy for archive_campaign. 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_campaign? +

archive_campaign 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.