AI agents use vast_update_tracking 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 tracking ID |
url | string | — | Tracking URL |
name | string | — | Tracking name |
event | string | — | Tracking event type |
Parameters from the server's own tool schema.
This tool modifies tracking configuration within the AdButler ad management system but does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial). The 'update' operation is reversible and represents a Write action.
From the tool's definition Tool name 'vast_update_tracking' and description 'Update an existing VAST tracking entry' indicate modification of existing data. VAST (Video Ad Serving Template) tracking entries are configuration objects used in ad delivery systems.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Update an existing VAST tracking entry. 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_tracking accepts 4 parameters: id, url, name, event. 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_tracking: 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_tracking 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_tracking 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_tracking. 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_tracking 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 →