AI agents call get_display_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, channel, geo-target, ad-item |
zones | string | — | Filter by zone IDs (comma-separated) |
period | string | Yes | Data grouping period: day, week, month, year |
preset | string | — | Date preset: today, last-24-hours, yesterday, this-week, last-week, this-month, last-month, year-to-date, last-year, last-7-days, last-14-days, last-30-days, la |
details | boolean | — | Include detailed breakdown |
summary | boolean | — | Include summary data |
timezone | string | — | Timezone for preset (e.g. "America/New_York") |
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 only retrieves and queries existing report data (impressions, clicks, CTR). It does not create, modify, delete, execute commands, or involve financial transactions. The 'get' prefix and 'report' retrieval purpose confirm it is a Read operation with minimal blast radius if misused—an AI agent could only access advertising performance metrics.
From the tool's definition Tool name 'get_display_report' and description 'Get display advertising report with impressions, clicks, and CTR' indicate retrieval of advertising metrics and analytics data with no modification or side effects.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Get display advertising report with impressions, clicks, and CTR. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_display_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_display_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_display_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_display_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_display_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_display_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 →