This record as markdown: /tools/adbutler/vast42-update-ad.md
What vast42_update_ad does on AdButler
AI agents use vast42_update_ad 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 | VAST 4.2 ad item ID |
name | string | — | Ad item name |
active | boolean | — | Whether ad item is active |
location | string | — | VAST tag URL or media location |
Parameters from the server's own tool schema.
Why vast42_update_ad is rated Medium
Updating a VAST 4.2 ad item modifies campaign/advertising data reversibly. This is a Write operation (not Destructive, since updates are generally reversible unless the implementation forcibly overwrites without recovery).
From the tool's definition Tool name and description: 'vast42_update_ad' and 'Update a VAST 4.2 ad item' — the verb 'update' indicates modification of existing data.
Attacks that exploit this kind of access
The rule that runs vast42_update_ad 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_update_ad, this is the rule to start with:
vast42_update_ad 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 vast42_update_ad call is checked against it from then on.
Questions about vast42_update_ad
Update a VAST 4.2 ad item. 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.
vast42_update_ad accepts 4 parameters: id, name, active, location. 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_update_ad: 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_update_ad 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 vast42_update_ad 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_update_ad. 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_update_ad 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