AI agents use vast42_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 |
|---|---|---|---|
zone | number | — | VAST zone ID |
active | boolean | — | Whether placement is active |
channel | number | — | VAST channel ID |
priority | number | — | Priority level |
schedule | number | — | Schedule ID |
advertisement | object | Yes | Advertisement object with id and type |
Parameters from the server's own tool schema.
This tool creates a new VAST (Video Ad Serving Template) placement, which is a write operation that adds new data to the AdButler system. It is reversible (placements can typically be deleted or archived, as evidenced by sibling tools like 'archive_zone' and 'archive_campaign'), so it does not rise to Destructive. It does not execute arbitrary code or trigger external operations, so it is not Execute.
From the tool's definition Tool name: 'vast42_create_placement' describes creating a VAST 4.2 placement. The description states 'Create a VAST 4.2 placement', which is a create operation that modifies ad campaign data.
Attacks that exploit this kind of access
Create a VAST 4.2 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.
vast42_create_placement accepts 6 parameters: zone, active, channel, priority, schedule, advertisement. Required: 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 vast42_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.
vast42_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 vast42_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 vast42_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.
vast42_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 →