This record as markdown: /tools/adbutler/create-channel.md
What create_channel does on AdButler
AI agents use create_channel 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 | Yes | Channel name |
priority | string | — | Serving priority (default: standard) |
use_share_of_voice | boolean | — | Whether to use share of voice as serving strategy (false = use weight) |
Parameters from the server's own tool schema.
Why create_channel is rated Medium
This tool creates new data (a channel entity) in the AdButler system. Creation is reversible—channels can be archived or deleted—so it does not qualify as Destructive. It performs no financial transactions, code execution, or external operations, making Write the appropriate category.
From the tool's definition Tool name 'create_channel' and description 'Create a new channel' indicate data creation without deletion or destruction.
Attacks that exploit this kind of access
The rule that runs create_channel 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_channel, this is the rule to start with:
create_channel 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_channel call is checked against it from then on.
Questions about create_channel
Create a new channel. 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_channel accepts 3 parameters: name, priority, use_share_of_voice. Required: name. 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_channel: 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_channel 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_channel 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_channel. 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_channel 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