AI agents use vast_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 to actively serve ads (defaults to true) |
ad_item | number | Yes | VAST ad item ID |
campaign | number | Yes | VAST campaign ID |
Parameters from the server's own tool schema.
This tool creates or establishes a new relationship between an ad item and a campaign, modifying system state by adding a campaign assignment record. This is reversible (can be unassigned/deleted) and does not permanently destroy data or execute arbitrary code, making it a Write action.
From the tool's definition Tool name contains 'create' and description states 'assign an ad item to a campaign' — this creates a new association/assignment record in the AdButler system.
Attacks that exploit this kind of access
Create a VAST 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.
vast_create_campaign_assignment accepts 3 parameters: active, ad_item, campaign. Required: 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 vast_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.
vast_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 vast_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 vast_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.
vast_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 →