AI agents use update_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 |
|---|---|---|---|
id | number | Yes | Ad item ID |
name | string | — | Ad item name |
location | string | — | Click-through URL |
metadata | object | — | Custom metadata key-value pairs |
tracking_pixel | string | — | Third-party tracking pixel URL |
tracking_pixels | array | — | Array of tracking pixel URLs |
catalog_item_identifier | string | — | Unique identifier for the catalog item |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly by updating an ad item in a catalog. It is not Read (no retrieval-only operation), not Execute (no code/command execution), not Destructive (updates are reversible), and not Financial (no money movement).
From the tool's definition Tool name contains 'update' and description states 'Update an existing catalog ad item', indicating modification of existing data.
Attacks that exploit this kind of access
Update an existing 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.
update_catalog_ad_item accepts 7 parameters: id, name, location, metadata, tracking_pixel, tracking_pixels, catalog_item_identifier. 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_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.
update_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 update_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 update_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.
update_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 →