AI agents use 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 | Zone ID |
name | string | — | Zone name |
width | number | — | Zone width in pixels |
height | number | — | Zone height in pixels |
metadata | object | — | Custom metadata key-value pairs |
bid_floor | number | — | Default bid floor |
pmp_deals | array | — | Allowed PMP Deal IDs |
publisher | number | — | Publisher ID |
dimensions | string | — | Zone dimensions type |
min_payout | number | — | Minimum payout per impression (CPM) |
responsive | string | — | Size behavior |
burn_in_hours | number | — | Hours before eCPM confidence |
Parameters from the server's own tool schema.
The tool modifies an existing zone reversibly—zone updates can be changed or reverted, distinguishing this from destructive operations (archive/delete). It does not create new zones (pure Write) nor does it execute arbitrary code or have financial implications.
From the tool's definition Tool name 'update_zone' and description 'Update an existing standard zone' indicate modification of existing data (zone configuration/properties).
Risk signalsHigh parameter count (31 properties)
Attacks that exploit this kind of access
Update an existing standard 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.
update_zone accepts 12 parameters: id, name, width, height, metadata, bid_floor, pmp_deals, publisher, dimensions, min_payout, responsive, burn_in_hours. 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 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.
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 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 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.
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 →