AI agents use vast_update_placement 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 placement ID |
cost | object | — | Pricing model: fixed_cost OR cpm/cpc/cpa |
zone | number | — | VAST zone ID (mutually exclusive with channel) |
active | boolean | — | Whether placement is active |
payout | object | — | Publisher payout configuration |
channel | number | — | VAST channel ID (mutually exclusive with zone) |
priority | number | — | Priority level |
schedule | number | — | VAST schedule ID |
serve_method | string | — | Serving system: weight-based or auction-based |
advertisement | object | — | Advertisement object with id and type |
max_frequency | number | — | Frequency cap limit |
data_key_target_id | number | — | Data Key Target ID (Enterprise only) |
Parameters from the server's own tool schema.
This tool modifies existing ad serving data (VAST placements) which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or trigger financial transactions (would be Financial). The medium severity reflects that misconfigured ad placements could impact ad campaign performance and revenue, but the operation itself is not irreversible.
From the tool's definition Tool name 'vast_update_placement' and description 'Update an existing VAST placement' indicate a modification operation on VAST (Video Ad Serving Template) placement configuration data.
Risk signalsHigh parameter count (25 properties)
Attacks that exploit this kind of access
Update an existing VAST placement. 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_placement accepts 12 parameters: id, cost, zone, active, payout, channel, priority, schedule, serve_method, advertisement, max_frequency, data_key_target_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_update_placement: 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_placement 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_placement 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_placement. 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_placement 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 →