bulk_upload_product_catalog
Bulk upload items to a product catalog
This record as markdown: /tools/adbutler/bulk-upload-product-catalog.md
What bulk_upload_product_catalog does on AdButler
AI agents use bulk_upload_product_catalog 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 |
|---|---|---|---|
catalog_id | number | Yes | Catalog ID |
publisher_id | number | Yes | Publisher ID |
Parameters from the server's own tool schema.
Why bulk_upload_product_catalog is rated Medium
This tool creates or modifies product catalog data in bulk, which is a reversible write operation. While bulk operations carry higher risk due to scale (potentially affecting many records at once), the operation itself is not destructive (data can be modified or removed later), not financial, and not executing arbitrary code.
From the tool's definition Tool name 'bulk_upload_product_catalog' and description 'Bulk upload items to a product catalog' indicate creation or modification of data in bulk. The 'bulk_upload' action is a write operation that creates or modifies product catalog entries.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_upload_product_catalog 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 bulk_upload_product_catalog, this is the rule to start with:
bulk_upload_product_catalog 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 bulk_upload_product_catalog call is checked against it from then on.
Questions about bulk_upload_product_catalog
Bulk upload items to a product catalog. 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.
bulk_upload_product_catalog accepts 2 parameters: catalog_id, publisher_id. Required: catalog_id, 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 bulk_upload_product_catalog: 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.
bulk_upload_product_catalog 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 bulk_upload_product_catalog 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 bulk_upload_product_catalog. 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.
bulk_upload_product_catalog 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