AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Zone name |
width | number | — | Zone width in pixels (must be 0 if dimensions is "dynamic") |
height | number | — | Zone height in pixels (must be 0 if dimensions is "dynamic") |
metadata | object | — | Custom metadata key-value pairs |
bid_floor | number | — | Default bid floor for programmatic |
pmp_deals | array | — | Allowed PMP Deal IDs |
publisher | number | — | Publisher ID |
dimensions | string | — | Zone dimensions type: "fixed" (default) or "dynamic" |
min_payout | number | — | Minimum payout per impression (CPM) |
responsive | string | — | Size behavior |
burn_in_hours | number | — | Hours before eCPM confidence |
refresh_limit | number | — | Total times zone will refresh |
Parameters from the server's own tool schema.
This tool creates new data objects (zones) in the AdButler system, which is a reversible Write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), move money (would be Financial), or merely retrieve information (would be Read).
From the tool's definition The tool description states it "Create[s] a new standard zone" which is a data creation operation. The parameters allow configurable dimensions (dynamic vs fixed sizing), indicating it creates new advertising zones with reversible effects.
Risk signalsHigh parameter count (31 properties)
Attacks that exploit this kind of access
Create a new standard zone. Set dimensions to "dynamic" for a dynamic zone (width/height must be 0), or "fixed" (default) for a fixed-size 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.
create_zone accepts 12 parameters: name, width, height, metadata, bid_floor, pmp_deals, publisher, dimensions, min_payout, responsive, burn_in_hours, refresh_limit. Required: name. 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 create_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.
create_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 create_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 create_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.
create_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 →