unarchive_advertiser
Restore an archived advertiser back to active status
This record as markdown: /tools/adbutler/unarchive-advertiser.md
What unarchive_advertiser does on AdButler
AI agents use unarchive_advertiser 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 advertiser ID |
Parameters from the server's own tool schema.
Why unarchive_advertiser is rated Medium
This tool modifies the status of an advertiser from archived to active. While it changes data, it is reversible (the advertiser can be archived again), making it a Write operation rather than Destructive. The medium severity reflects the potential business impact of reactivating advertisers (e.g., resuming campaigns, financial obligations), but without direct financial movement or data deletion.
From the tool's definition Tool name 'unarchive_advertiser' and description 'Restore an archived advertiser back to active status' indicate a state-changing operation that reverses a previous destructive action (archive) but does not itself delete data irreversibly.
Attacks that exploit this kind of access
The rule that runs unarchive_advertiser 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_advertiser, this is the rule to start with:
unarchive_advertiser 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_advertiser call is checked against it from then on.
Questions about unarchive_advertiser
Restore an archived advertiser 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_advertiser 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_advertiser: 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_advertiser 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_advertiser 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_advertiser. 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_advertiser 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