unarchive_campaign
Restore an archived standard campaign back to active status
This record as markdown: /tools/adbutler/unarchive-campaign.md
What unarchive_campaign does on AdButler
AI agents use unarchive_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Archived campaign ID |
Parameters from the server's own tool schema.
Why unarchive_campaign is rated Medium
This tool modifies the state of a campaign record, making it active again. While it does restore a prior state (reversible in theory), the action itself constitutes a Write operation that changes campaign metadata and visibility in the system. It is not destructive since archiving is typically reversible and data is not deleted.
From the tool's definition Tool name is 'unarchive_campaign' and description states 'Restore an archived standard campaign back to active status' — this reverses an archive action by modifying campaign state from archived to active.
Attacks that exploit this kind of access
The rule that runs unarchive_campaign 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 unarchive_campaign, this is the rule to start with:
unarchive_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.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every unarchive_campaign call is checked against it from then on.
Questions about unarchive_campaign
Restore an archived standard campaign back to active status. 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.
unarchive_campaign 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 unarchive_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.
unarchive_campaign 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 unarchive_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.
Set action: deny in the PolicyLayer policy for unarchive_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.
unarchive_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue