get_demand_source_report
Get demand source statistics report
This record as markdown: /tools/adbutler/get-demand-source-report.md
What get_demand_source_report does on AdButler
AI agents call get_demand_source_report to retrieve information from AdButler without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
preset | string | — | Date preset |
timezone | string | — | Timezone |
Parameters from the server's own tool schema.
Why get_demand_source_report is rated Low
This tool retrieves or queries demand source statistics—a classic Read operation. It has no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal, as an AI agent could only access existing statistics data. The server context shows other tools on the server perform archive, bulk create, and bulk upload operations (more severe), but this tool itself is purely informational.
From the tool's definition Tool name 'get_demand_source_report' and description 'Get demand source statistics report' indicate a retrieval operation that queries existing report data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_demand_source_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_demand_source_report, this is the rule to start with:
get_demand_source_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every get_demand_source_report call is checked against it from then on.
Questions about get_demand_source_report
Get demand source statistics report. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_demand_source_report accepts 2 parameters: preset, timezone. 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_demand_source_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_demand_source_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_demand_source_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_demand_source_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_demand_source_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue