AI agents use vast42_update_interactive_creative_file 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 4.2 interactive creative file ID |
name | string | — | Interactive creative file name |
mime_type | string | — | MIME type |
Parameters from the server's own tool schema.
This tool modifies creative files used in ad campaigns (VAST is a video ad serving standard). Updates are reversible—the previous version can be restored—so this is Write rather than Destructive. However, advertising content modifications in a campaign management platform carry medium severity due to potential for misuse affecting live ad campaigns and audience exposure.
From the tool's definition Tool name explicitly contains 'update' and description states 'Update a VAST 4.2 interactive creative file' — indicates modification of existing advertising creative assets.
Attacks that exploit this kind of access
Update a VAST 4.2 interactive creative file. 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_update_interactive_creative_file accepts 3 parameters: id, name, mime_type. 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 vast42_update_interactive_creative_file: 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_update_interactive_creative_file 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_update_interactive_creative_file 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_update_interactive_creative_file. 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_update_interactive_creative_file 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 →