AI agents use vast42_update_non_linear 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 non-linear media ID |
name | string | — | Non-linear media name |
width | number | — | Width in pixels |
height | number | — | Height in pixels |
mime_type | string | — | MIME type |
Parameters from the server's own tool schema.
This tool modifies VAST (Video Ad Serving Template) 4.2 non-linear media metadata or configuration. While it alters ad serving data that could affect campaigns, the operation is reversible (can be updated again or reverted). It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is limited to advertising configuration within AdButler campaigns, justifying medium severity.
From the tool's definition Tool name 'vast42_update_non_linear' and description 'Update a VAST 4.2 non-linear media' indicate modification of advertising media configuration. 'Update' is a write operation that modifies existing data.
Attacks that exploit this kind of access
Update a VAST 4.2 non-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.
vast42_update_non_linear accepts 5 parameters: id, name, width, height, 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_non_linear: 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_non_linear 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_non_linear 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_non_linear. 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_non_linear 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 →