list_all_report_schedules
List all report schedules across all configurations
This record as markdown: /tools/adbutler/list-all-report-schedules.md
What list_all_report_schedules does on AdButler
AI agents call list_all_report_schedules 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 |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
Parameters from the server's own tool schema.
Why list_all_report_schedules is rated Low
This tool performs a query/list operation to retrieve existing report schedule configurations. It reads data without creating, modifying, deleting, or executing any actions. The verb 'list' and lack of any action descriptor confirm this is a passive Read operation with minimal security risk.
From the tool's definition Tool name 'list_all_report_schedules' and description 'List all report schedules across all configurations' indicate a retrieval operation with no mutation or side effects.
Attacks that exploit this kind of access
The rule that runs list_all_report_schedules 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 list_all_report_schedules, this is the rule to start with:
list_all_report_schedules 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 list_all_report_schedules call is checked against it from then on.
Questions about list_all_report_schedules
List all report schedules across all configurations. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_all_report_schedules accepts 2 parameters: limit, offset. 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 list_all_report_schedules: 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.
list_all_report_schedules 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 list_all_report_schedules 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 list_all_report_schedules. 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.
list_all_report_schedules 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