AI agents use create_campaign_assignment 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 |
|---|---|---|---|
active | boolean | — | Whether assignment is active (defaults to true) |
weight | number | — | Relative delivery weight (defaults to 1) |
campaign | object | Yes | Campaign object with id and type |
keywords | string | — | Comma-separated keywords for targeting |
schedule | number | — | Schedule ID (only if campaign scheduling_source is "AD_ITEM") |
geo_target | number | — | Geo Target ID (only if campaign targeting_source is "AD_ITEM") |
list_target | number | — | List Target ID |
advertisement | object | Yes | Advertisement object with id and type |
data_key_target | number | — | Data Key Target ID |
platform_target | number | — | Platform Target ID |
keywords_match_method | string | — | Keyword matching method |
Parameters from the server's own tool schema.
This tool creates a new association/assignment between an ad item and a campaign. This is a Write operation because it creates or modifies data (campaign assignments) in a reversible manner. It does not execute arbitrary code, delete data permanently, move money, or read-only retrieve information.
From the tool's definition Tool name and description indicate 'Create a new campaign assignment' — a reversible data creation action that assigns an ad item to a campaign in the AdButler advertising platform.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
Create a new campaign assignment (assign an ad item to 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.
create_campaign_assignment accepts 11 parameters: active, weight, campaign, keywords, schedule, geo_target, list_target, advertisement, data_key_target, platform_target, keywords_match_method. Required: campaign, advertisement. 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_assignment: 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_assignment 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_assignment 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_assignment. 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_assignment 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →