create_product_source_target
Create a new product source target for a publisher
This record as markdown: /tools/adbutler/create-product-source-target.md
What create_product_source_target does on AdButler
AI agents use create_product_source_target 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 | — | Source target name |
source_id | number | — | Source ID to target |
publisher_id | number | Yes | Publisher ID |
Parameters from the server's own tool schema.
Why create_product_source_target is rated Medium
This tool creates a new entity (product source target) for a publisher in the AdButler ad management system. Creation of new resources is a reversible Write operation—the created target can typically be modified or deleted later. The severity is medium because misuse could create unwanted targeting configurations affecting ad campaigns, but the impact is limited to one publisher's targeting and is reversible.
From the tool's definition Tool name and description indicate it 'Create[s] a new product source target' — the verb 'create' and action 'Create a new' denote data creation, which is a Write operation.
Attacks that exploit this kind of access
The rule that runs create_product_source_target 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 create_product_source_target, this is the rule to start with:
create_product_source_target 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 create_product_source_target call is checked against it from then on.
Questions about create_product_source_target
Create a new product source target for a publisher. 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_product_source_target accepts 3 parameters: name, source_id, publisher_id. Required: 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 create_product_source_target: 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_product_source_target 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_product_source_target 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_product_source_target. 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_product_source_target 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