This record as markdown: /tools/adbutler/update-email-zone.md
What update_email_zone does on AdButler
AI agents use update_email_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 | Email 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 |
publisher | number | — | Publisher ID |
uid_rotate | boolean | — | Serve different ads per user |
rotate_timer | object | — | Period after which user sees a new ad |
auction_tie_break | string | — | Tie-breaking method |
Parameters from the server's own tool schema.
Why update_email_zone is rated Medium
This tool modifies an existing email zone configuration in the AdButler ad management system. It is categorized as Write because it creates or modifies data reversibly—zone configurations can be updated and reverted. It is not Destructive because updates are not permanent deletions.
From the tool's definition Tool name 'update_email_zone' and description 'Update an existing email zone' indicate modification of an existing resource.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs update_email_zone 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 update_email_zone, this is the rule to start with:
update_email_zone 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 update_email_zone call is checked against it from then on.
Questions about update_email_zone
Update an existing email 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_email_zone accepts 9 parameters: id, name, width, height, metadata, publisher, uid_rotate, rotate_timer, auction_tie_break. 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_email_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_email_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_email_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_email_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_email_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue