unarchive_channel
Restore an archived channel back to active status
This record as markdown: /tools/adbutler/unarchive-channel.md
What unarchive_channel does on AdButler
AI agents use unarchive_channel 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 channel ID |
Parameters from the server's own tool schema.
Why unarchive_channel is rated Medium
This tool modifies channel state by restoring it from archived to active status. It is reversible (can be re-archived if needed) and does not delete data or move money, making it a Write operation. Severity is medium because misuse could reactivate inappropriate advertising channels, but the effect is not financially harmful or permanently destructive.
From the tool's definition Tool name 'unarchive_channel' and description 'Restore an archived channel back to active status' indicate a state-change operation that reverses a previous archival action, modifying data (channel status) without irreversible deletion.
Attacks that exploit this kind of access
The rule that runs unarchive_channel 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_channel, this is the rule to start with:
unarchive_channel 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_channel call is checked against it from then on.
Questions about unarchive_channel
Restore an archived channel 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_channel 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_channel: 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_channel 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_channel 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_channel. 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_channel 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