AI agents call list_report_schedules 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 |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
report_config_id | number | Yes | Report configuration ID |
Parameters from the server's own tool schema.
This tool retrieves scheduling information about reports. It performs a query/retrieval operation ('list') without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal — an agent could view report schedules but cannot alter campaigns, delete data, or trigger financial transactions. This is a straightforward Read operation.
From the tool's definition Tool name is 'list_report_schedules' and description states it 'List schedules for a specific report configuration' — the verb 'list' and action of retrieving/querying schedules indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
List schedules for a specific report configuration. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_report_schedules accepts 3 parameters: limit, offset, report_config_id. Required: report_config_id. 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_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_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_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_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_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.
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 →