This record as markdown: /tools/adbutler/vast42-delete-companion.md
What vast42_delete_companion does on AdButler
AI agents call vast42_delete_companion 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 | VAST 4.2 companion ID |
Parameters from the server's own tool schema.
Why vast42_delete_companion is rated Critical
This tool permanently removes ad creative data (VAST 4.2 companion ads) from the AdButler system. Deletion is an irreversible destructive action that cannot be undone. An AI agent misusing this could eliminate critical advertising assets, causing business impact. While scoped to a specific ad type, the permanent data loss justifies 'high' severity and 'Destructive' category per the hierarchy rule.
From the tool's definition Tool name 'vast42_delete_companion' explicitly contains 'delete', and description states 'Delete a VAST 4.2 companion'. VAST companions are ad creative elements. The delete operation is irreversible.
Attacks that exploit this kind of access
The rule that runs vast42_delete_companion 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 vast42_delete_companion, this is the rule to start with:
vast42_delete_companion 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 vast42_delete_companion call is checked against it from then on.
Questions about vast42_delete_companion
Delete a VAST 4.2 companion. 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.
vast42_delete_companion 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 vast42_delete_companion: 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.
vast42_delete_companion 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 vast42_delete_companion 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 vast42_delete_companion. 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.
vast42_delete_companion 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