AI agents call get_vast_report to retrieve information from AdButler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Report type: overview, advertiser, publisher, zone, campaign, ad-item |
zones | string | — | Filter by zone IDs (comma-separated) |
period | string | Yes | Data grouping period: day, week, month, year |
preset | string | — | Date preset (same options as display report) |
details | boolean | — | Include detailed breakdown |
summary | boolean | — | Include summary data |
timezone | string | — | Timezone for preset |
breakdown | boolean | — | Include breakdown data |
campaigns | string | — | Filter by campaign IDs (comma-separated) |
financials | boolean | — | Include financial data |
publishers | string | — | Filter by publisher IDs (comma-separated) |
advertisers | string | — | Filter by advertiser IDs (comma-separated) |
Parameters from the server's own tool schema.
This tool retrieves and queries advertising report data without side effects. The 'get' verb combined with 'report' clearly indicates a read-only operation that accesses data about VAST video campaigns. No creation, modification, deletion, or execution of external operations is implied. The blast radius of misuse is minimal—an agent retrieving reports poses low risk to the AdButler system.
From the tool's definition Tool name 'get_vast_report' and description 'Get VAST video advertising report' indicate retrieval of existing report data with no modification or deletion.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
Get VAST video advertising report. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_vast_report accepts 12 parameters: type, zones, period, preset, details, summary, timezone, breakdown, campaigns, financials, publishers, advertisers. Required: type, period. 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 get_vast_report: 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.
get_vast_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_vast_report 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 get_vast_report. 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.
get_vast_report 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 →