unarchive_publisher
Restore an archived publisher back to active status
This record as markdown: /tools/adbutler/unarchive-publisher.md
What unarchive_publisher does on AdButler
AI agents use unarchive_publisher 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 publisher ID |
Parameters from the server's own tool schema.
Why unarchive_publisher is rated Medium
This tool restores archived data to active status, which is a write operation that modifies publisher metadata. It is reversible (can be archived again), so it does not qualify as Destructive. The blast radius is medium because incorrect restoration could activate unintended publishers in ad campaigns, potentially causing billing or operational issues, but the change is not permanent and can be undone.
From the tool's definition Tool name 'unarchive_publisher' and description 'Restore an archived publisher back to active status' indicate a state-change operation that modifies publisher records reversibly.
Attacks that exploit this kind of access
The rule that runs unarchive_publisher 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_publisher, this is the rule to start with:
unarchive_publisher 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_publisher call is checked against it from then on.
Questions about unarchive_publisher
Restore an archived publisher 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_publisher 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_publisher: 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_publisher 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_publisher 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_publisher. 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_publisher 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