AI agents use vast_update_linear_media 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 linear media ID |
name | string | — | Linear media name |
bitrate | number | — | Bitrate in kbps |
duration | number | — | Duration in seconds |
mime_type | string | — | MIME type (e.g. video/mp4) |
Parameters from the server's own tool schema.
This tool modifies VAST (Video Ad Serving Template) linear media configuration, which is a reversible change to advertising campaign assets. The blast radius is medium because misconfigured VAST updates could cause ad serving issues, incorrect video playback, or campaign malfunction, but the change can be rolled back by updating again.
From the tool's definition Tool name is 'vast_update_linear_media' with description 'Update an existing VAST linear media'. The verb 'update' indicates modification of existing data, fitting the Write category (creates or modifies data reversibly).
Attacks that exploit this kind of access
Update an existing VAST linear media. 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_linear_media accepts 5 parameters: id, name, bitrate, duration, 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 vast_update_linear_media: 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_linear_media 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_linear_media 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_linear_media. 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_linear_media 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 →