vast_update_channel_zone_assignment
Update a VAST channel zone assignment
This record as markdown: /tools/adbutler/vast-update-channel-zone-assignment.md
What vast_update_channel_zone_assignment does on AdButler
AI agents use vast_update_channel_zone_assignment 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 channel zone assignment ID |
zone | number | — | VAST zone ID |
channel | number | — | VAST channel ID |
Parameters from the server's own tool schema.
Why vast_update_channel_zone_assignment is rated Medium
The tool creates or modifies data (channel-zone assignment configuration) in a reversible manner, characteristic of Write category. While it could affect ad delivery if misconfigured, it does not delete data, execute arbitrary code, move money, or trigger irreversible actions.
From the tool's definition Tool name and description indicate 'Update' operation on VAST channel zone assignment, modifying existing configuration data. This is a reversible change to ad campaign infrastructure.
Attacks that exploit this kind of access
The rule that runs vast_update_channel_zone_assignment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vast_update_channel_zone_assignment, this is the rule to start with:
vast_update_channel_zone_assignment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every vast_update_channel_zone_assignment call is checked against it from then on.
Questions about vast_update_channel_zone_assignment
Update a VAST channel zone assignment. 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_channel_zone_assignment accepts 3 parameters: id, zone, channel. 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_channel_zone_assignment: 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_channel_zone_assignment 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_channel_zone_assignment 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_channel_zone_assignment. 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_channel_zone_assignment 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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue