AI agents call get_click_details_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 |
|---|---|---|---|
zones | string | — | Filter by zone IDs (comma-separated) |
preset | string | — | Date preset |
timezone | string | — | Timezone |
campaigns | string | — | Filter by campaign IDs (comma-separated) |
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 analytics/report data (click details) from AdButler campaigns. 'Get' operations are read-only with no side effects. No data creation, modification, deletion, code execution, or financial transactions are involved. The blast radius of misuse is minimal—an agent could only access click metrics they may not be authorized to see, which is a confidentiality concern but not operationally destructive.
From the tool's definition Tool name 'get_click_details_report' and description 'Get click details report' indicate a retrieval operation that queries existing report data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get click details report. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_click_details_report accepts 6 parameters: zones, preset, timezone, campaigns, publishers, advertisers. 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_click_details_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_click_details_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_click_details_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_click_details_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_click_details_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 →