AI agents use update_catalog_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 | Catalog zone ID |
name | string | — | Zone name |
auction_type | string | — | Auction type |
bid_floor_cpc | number | — | CPC bid floor |
bid_floor_cpm | number | — | CPM bid floor |
advertiser_cost_type | string | — | Billing model |
click_cooldown_period | number | — | Click cooldown period in seconds |
conversion_lookback_period | number | — | Conversion lookback period in seconds |
Parameters from the server's own tool schema.
The tool modifies (updates) an existing catalog zone configuration within the AdButler advertising management system. This is a reversible Write operation—the zone can be modified again or reverted. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read).
From the tool's definition Tool name is 'update_catalog_zone' and description states 'Update an existing catalog zone', indicating modification of an existing resource.
Attacks that exploit this kind of access
Update an existing catalog 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_catalog_zone accepts 8 parameters: id, name, auction_type, bid_floor_cpc, bid_floor_cpm, advertiser_cost_type, click_cooldown_period, conversion_lookback_period. 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_catalog_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_catalog_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_catalog_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_catalog_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_catalog_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 →