AI agents use vast_update_zone 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 zone ID |
name | string | — | Zone name |
metadata | object | — | Custom metadata key-value pairs |
publisher | number | — | Publisher ID |
default_vast_ad_item | number | — | Default VAST ad item ID (mutually exclusive with default_vast_campaign) |
serve_priority_order | string | — | Priority order for serving: "weight" or "auction" |
default_vast_campaign | number | — | Default VAST campaign ID (mutually exclusive with default_vast_ad_item) |
Parameters from the server's own tool schema.
The tool modifies (updates) an existing VAST zone configuration, which is a reversible change to advertising infrastructure. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve data (Read). Write category is appropriate because updates can typically be undone or rolled back.
From the tool's definition Tool name 'vast_update_zone' and description 'Update an existing VAST zone' indicate modification of an existing configuration or resource.
Attacks that exploit this kind of access
Update an existing VAST zone. 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_zone accepts 7 parameters: id, name, metadata, publisher, default_vast_ad_item, serve_priority_order, default_vast_campaign. 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_zone: 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_zone 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_zone 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_zone. 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_zone 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 →