AI agents use vast_update_schedule 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 schedule ID |
end_date | string | — | End date (YYYY-MM-DD HH:MM:SS), null for indefinite |
geo_target | number | — | Geotarget ID (0 = no targeting) |
quota_type | string | — | Quota measurement type |
start_date | string | — | Start date (YYYY-MM-DD HH:MM:SS) |
day_parting_id | number | — | Day parting ID for time-of-day targeting |
quota_lifetime | number | — | Total quota amount (views or clicks, not per thousand) |
delivery_method | string | — | Delivery pacing: "default" (ASAP) or "smooth" (evenly distributed) |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly—updating a schedule is a write operation. It does not execute arbitrary code or commands (Execute), does not permanently destroy data (Destructive), and does not involve money movement (Financial).
From the tool's definition Tool name 'vast_update_schedule' and description 'Update an existing VAST schedule' indicate modification of an existing configuration or schedule. VAST (Video Ad Serving Template) schedules control ad delivery timing and behavior.
Attacks that exploit this kind of access
Update an existing VAST schedule. 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_schedule accepts 8 parameters: id, end_date, geo_target, quota_type, start_date, day_parting_id, quota_lifetime, delivery_method. 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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 →