This record as markdown: /tools/adbutler/create-campaign.md
What create_campaign does on AdButler
AI agents use create_campaign 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 | Campaign name |
budget | object | — | Budget limits (daily/weekly/monthly/lifetime) |
contract | number | — | Contract ID (requires Contract Management add-on) |
metadata | object | — | Custom metadata key-value pairs |
advertiser | number | — | Advertiser ID |
roadblock_tags | string | — | Tag to link campaign to a roadblock |
targeting_source | string | — | Whether targeting is set at campaign or ad item level |
scheduling_source | string | — | Whether scheduling is set at campaign or ad item level |
trusted_redirect_domains | array | — | Array of trusted redirect domains |
Parameters from the server's own tool schema.
Why create_campaign is rated Medium
This tool creates (writes) a new campaign, which is a reversible operation. It does not execute arbitrary code, delete data irreversibly, or move money. The moderate severity reflects that creating campaigns could impact ad spending and business operations, but the action is reversible (campaigns can be archived as evidenced by sibling tool 'archive_campaign').
From the tool's definition Tool name 'create_campaign' and description 'Create a new standard campaign' indicate creation of a new advertising campaign resource.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs create_campaign 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_campaign, this is the rule to start with:
create_campaign 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_campaign call is checked against it from then on.
Questions about create_campaign
Create a new standard 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.
create_campaign accepts 9 parameters: name, budget, contract, metadata, advertiser, roadblock_tags, targeting_source, scheduling_source, trusted_redirect_domains. 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_campaign: 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_campaign 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_campaign 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_campaign. 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_campaign 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