AI agents use vast_update_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 |
|---|---|---|---|
id | number | Yes | VAST campaign ID |
name | string | — | Campaign name |
contract | number | — | Contract ID (requires Contract Management add-on) |
advertiser | number | — | Advertiser ID |
Parameters from the server's own tool schema.
The tool creates or modifies campaign data in the AdButler advertising system. While updates are generally reversible (Write category), the severity is elevated to 'high' because: (1) VAST campaigns control programmatic ad delivery and spending, (2) misuse could redirect ad spend, alter targeting, or modify campaign parameters affecting real advertising operations and potentially financial outcomes, and (3) the…
From the tool's definition Tool name contains 'update' and description states 'Update an existing VAST campaign' — this modifies campaign data reversibly without deletion.
Attacks that exploit this kind of access
Update an existing VAST 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_update_campaign accepts 4 parameters: id, name, contract, advertiser. Required: id. 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_update_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.
vast_update_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 vast_update_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 vast_update_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.
vast_update_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.
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 →