vast_delete_archived_campaign
Permanently delete an archived VAST campaign
This record as markdown: /tools/adbutler/vast-delete-archived-campaign.md
What vast_delete_archived_campaign does on AdButler
AI agents call vast_delete_archived_campaign to permanently remove resources in AdButler, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Archived VAST campaign ID |
Parameters from the server's own tool schema.
Why vast_delete_archived_campaign is rated Critical
This tool irreversibly deletes data (an archived VAST campaign) with no undo capability. While the campaign is already archived (reducing some blast radius), permanent deletion cannot be reversed. Destructive category is more severe than Write, so it takes precedence. High severity reflects the permanent loss of campaign data, though the impact is somewhat limited to archived records rather than active campaigns.
From the tool's definition Tool name contains 'delete' and description states 'Permanently delete an archived VAST campaign'. The word 'Permanently' explicitly indicates an irreversible operation.
Attacks that exploit this kind of access
The rule that runs vast_delete_archived_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 vast_delete_archived_campaign, this is the rule to start with:
vast_delete_archived_campaign is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every vast_delete_archived_campaign call is checked against it from then on.
Questions about vast_delete_archived_campaign
Permanently delete an archived VAST campaign. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
vast_delete_archived_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 vast_delete_archived_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.
vast_delete_archived_campaign is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the vast_delete_archived_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 vast_delete_archived_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.
vast_delete_archived_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.
Across the catalogue