vast42_create_campaign_assignment
Create a VAST 4.2 campaign assignment
This record as markdown: /tools/adbutler/vast42-create-campaign-assignment.md
What vast42_create_campaign_assignment does on AdButler
AI agents use vast42_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 |
ad_item | number | — | VAST ad item ID |
campaign | number | — | VAST campaign ID |
Parameters from the server's own tool schema.
Why vast42_create_campaign_assignment is rated Medium
Creating a campaign assignment is a Write operation—it establishes a new configuration/binding in the AdButler system. While campaign assignments may influence ad delivery, the action itself is reversible (can be updated or deleted).
From the tool's definition Tool name 'vast42_create_campaign_assignment' with description 'Create a VAST 4.2 campaign assignment' indicates creation of a new campaign assignment resource, which is a reversible data modification operation.
Attacks that exploit this kind of access
The rule that runs vast42_create_campaign_assignment 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 vast42_create_campaign_assignment, this is the rule to start with:
vast42_create_campaign_assignment 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 vast42_create_campaign_assignment call is checked against it from then on.
Questions about vast42_create_campaign_assignment
Create a VAST 4.2 campaign assignment. 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.
vast42_create_campaign_assignment accepts 3 parameters: active, ad_item, campaign. 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 vast42_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.
vast42_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 vast42_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 vast42_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.
vast42_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue