AI agents use vast_update_ad_item 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 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.
This tool modifies VAST ad item configuration reversibly. While 'update' operations can have downstream effects (e.g., changing ad creative or targeting), the action itself is not destructive, financial, nor does it execute arbitrary code. The moderate severity reflects that misconfigured ad items could disrupt advertising campaigns or reach unintended audiences, but changes remain editable.
From the tool's definition Tool name contains 'update' and description states 'Update an existing VAST ad item', indicating modification of existing data without deletion or irreversible changes.
Attacks that exploit this kind of access
Update an existing VAST 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.
vast_update_ad_item 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 vast_update_ad_item: 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_update_ad_item 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 vast_update_ad_item 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_update_ad_item. 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_update_ad_item 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →