create_product_source
Create a new product source for a publisher
This record as markdown: /tools/adbutler/create-product-source.md
What create_product_source does on AdButler
AI agents use create_product_source 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 | — | Source URL |
name | string | — | Source name |
type | string | — | Source type |
publisher_id | number | Yes | Publisher ID |
Parameters from the server's own tool schema.
Why create_product_source is rated Medium
This tool creates a new product source, which is a reversible write operation. It modifies system state by adding a new record but does not delete data (ruling out Destructive), execute code (ruling out Execute), or move money (ruling out Financial).
From the tool's definition Tool description states 'Create a new product source' — a create operation that adds a new resource to the AdButler system.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs create_product_source 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, this is the rule to start with:
create_product_source 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 call is checked against it from then on.
Questions about create_product_source
Create a new product source 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 accepts 4 parameters: url, name, type, 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: 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 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 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. 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 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