AI agents use create_catalog_ad_item 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 | Ad item name |
location | string | — | Click-through URL |
metadata | object | — | Custom metadata key-value pairs |
catalog_id | number | Yes | Catalog ID |
tracking_pixel | string | — | Third-party tracking pixel URL |
tracking_pixels | array | — | Array of tracking pixel URLs |
catalog_item_identifier | string | Yes | Unique identifier for the catalog item |
Parameters from the server's own tool schema.
The tool creates new advertising content/data in the system. This is a reversible Write operation—the created ad item can be modified, archived (as evidenced by 'archive_*' sibling tools), or removed without permanent system damage. It does not execute arbitrary code, move money, or delete data.
From the tool's definition Tool name 'create_catalog_ad_item' explicitly performs a creation action ('create'). Description states 'Create a new catalog ad item', confirming this generates new data in the AdButler system without deletion or irreversible overwrites.
Attacks that exploit this kind of access
Create a new catalog ad item. 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_ad_item accepts 7 parameters: name, location, metadata, catalog_id, tracking_pixel, tracking_pixels, catalog_item_identifier. Required: name, catalog_id, catalog_item_identifier. 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_ad_item: 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_ad_item 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_ad_item 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_ad_item. 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_ad_item 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 →