update_product_catalog_item
Update an existing product catalog item
This record as markdown: /tools/adbutler/update-product-catalog-item.md
What update_product_catalog_item does on AdButler
AI agents use update_product_catalog_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 |
|---|---|---|---|
url | string | — | Item URL |
name | string | — | Item name |
price | string | — | Item price |
category | string | — | Item category |
image_url | string | — | Item image URL |
catalog_id | number | Yes | Catalog ID |
identifier | string | Yes | Unique identifier for the catalog item |
description | string | — | Item description |
publisher_id | number | Yes | Publisher ID |
Parameters from the server's own tool schema.
Why update_product_catalog_item is rated Medium
This tool modifies existing data (product catalog items) reversibly—updates can be undone or corrected. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial). The blast radius is medium because incorrect updates to ad product catalogs could affect ad serving and campaign performance, but changes are not irreversible.
From the tool's definition Tool name 'update_product_catalog_item' and description 'Update an existing product catalog item' indicate modification of data. The context shows this is part of an ad management system (AdButler) where product catalog items are core business data.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs update_product_catalog_item 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_product_catalog_item, this is the rule to start with:
update_product_catalog_item 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_product_catalog_item call is checked against it from then on.
Questions about update_product_catalog_item
Update an existing product catalog 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_product_catalog_item accepts 9 parameters: url, name, price, category, image_url, catalog_id, identifier, description, publisher_id. Required: catalog_id, identifier, publisher_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_product_catalog_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_product_catalog_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_product_catalog_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_product_catalog_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_product_catalog_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue