AI agents use vast_create_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 |
|---|---|---|---|
cost | object | — | Pricing model: fixed_cost OR cpm/cpc/cpa |
zone | number | — | VAST zone ID (required if channel not set; mutually exclusive with channel) |
active | boolean | — | Whether placement is active (defaults to true) |
payout | object | — | Publisher payout configuration |
channel | number | — | VAST channel ID (required if zone not set; mutually exclusive with zone) |
priority | number | — | Priority level (sponsorship, standard, network, bulk, house) |
schedule | number | Yes | VAST schedule ID |
serve_method | string | — | Serving system: weight-based or auction-based |
advertisement | object | Yes | Advertisement object with id and type |
max_frequency | number | — | Frequency cap limit |
data_key_target_id | number | — | Data Key Target ID (Enterprise only) |
max_frequency_type | string | — | Event type to count for frequency capping |
Parameters from the server's own tool schema.
This tool creates a new VAST placement by assigning ad items or campaigns to zones/channels. This is a reversible write operation that modifies advertising configuration. It does not delete data (not Destructive), execute arbitrary code (not Execute), handle financial transactions (not Financial), or merely read data (not Read).
From the tool's definition Tool description: 'Create a new VAST placement (assign a VAST ad item or campaign to a VAST zone or channel)' — the word 'Create' and 'assign' indicate data creation and modification operations.
Risk signalsHigh parameter count (24 properties)
Attacks that exploit this kind of access
Create a new VAST placement (assign a VAST ad item or campaign to a VAST zone or channel). 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_create_placement accepts 12 parameters: cost, zone, active, payout, channel, priority, schedule, serve_method, advertisement, max_frequency, data_key_target_id, max_frequency_type. Required: schedule, advertisement. 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_create_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_create_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_create_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_create_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_create_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 →