create_catalog_zone
Create a new catalog zone for product/retail ad serving
This record as markdown: /tools/adbutler/create-catalog-zone.md
What create_catalog_zone does on AdButler
AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Zone name |
bid_floor | number | — | Default bid floor |
publisher | number | — | Publisher ID |
catalog_id | number | Yes | Catalog ID |
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 (1-86400) |
conversion_lookback_period | number | — | Conversion lookback period in seconds (1-7776000) |
Parameters from the server's own tool schema.
Why create_catalog_zone is rated Medium
This tool creates a new advertising zone configuration for product/retail ad serving. It is reversible (zones can be archived/deleted by other tools), has no financial impact itself, and does not execute arbitrary code or delete data. The action is a straightforward creation of a new entity in the AdButler advertising platform.
From the tool's definition Tool name 'create_catalog_zone' and description 'Create a new catalog zone' indicate a creation/write operation.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs create_catalog_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 create_catalog_zone, this is the rule to start with:
create_catalog_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 create_catalog_zone call is checked against it from then on.
Questions about create_catalog_zone
Create a new catalog zone for product/retail ad serving. 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_catalog_zone accepts 10 parameters: name, bid_floor, publisher, catalog_id, auction_type, bid_floor_cpc, bid_floor_cpm, advertiser_cost_type, click_cooldown_period, conversion_lookback_period. Required: name, catalog_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 create_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.
create_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 create_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 create_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.
create_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue