campaign_bulk_create_catalog_ad_items
Bulk create catalog ad items in a campaign
This record as markdown: /tools/adbutler/campaign-bulk-create-catalog-ad-items.md
What campaign_bulk_create_catalog_ad_items does on AdButler
AI agents use campaign_bulk_create_catalog_ad_items 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 |
|---|---|---|---|
items | array | Yes | Array of catalog ad item objects to create |
campaign_id | number | Yes | Campaign ID |
Parameters from the server's own tool schema.
Why campaign_bulk_create_catalog_ad_items is rated Medium
This tool creates (writes) ad items in bulk within an advertising campaign. It modifies campaign data by adding new ad items, which is reversible (items can be archived or deleted). The 'bulk' operation and advertising campaign context give it higher severity than simple single-item creation due to potential for large-scale unintended data generation.
From the tool's definition Tool name contains 'bulk_create' and description states 'Bulk create catalog ad items in a campaign' — this creates multiple ad items, which are data objects within AdButler campaigns.
Attacks that exploit this kind of access
The rule that runs campaign_bulk_create_catalog_ad_items 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 campaign_bulk_create_catalog_ad_items, this is the rule to start with:
campaign_bulk_create_catalog_ad_items 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 campaign_bulk_create_catalog_ad_items call is checked against it from then on.
Questions about campaign_bulk_create_catalog_ad_items
Bulk create catalog ad items in a campaign. 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.
campaign_bulk_create_catalog_ad_items accepts 2 parameters: items, campaign_id. Required: items, campaign_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 campaign_bulk_create_catalog_ad_items: 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.
campaign_bulk_create_catalog_ad_items 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 campaign_bulk_create_catalog_ad_items 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 campaign_bulk_create_catalog_ad_items. 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.
campaign_bulk_create_catalog_ad_items 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