AI agents call get_report_schedule 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 |
|---|---|---|---|
schedule_id | number | Yes | Schedule ID |
report_config_id | number | Yes | Report configuration ID |
Parameters from the server's own tool schema.
This tool retrieves or queries existing report schedule data without creating, modifying, deleting, or executing operations. It is a straightforward read operation that poses minimal risk if misused by an AI agent, as it only surfaces information that likely already exists in the AdButler system.
From the tool's definition Tool name 'get_report_schedule' and description 'Get a specific report schedule' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get a specific report schedule. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_report_schedule accepts 2 parameters: schedule_id, report_config_id. Required: schedule_id, 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 get_report_schedule: 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_report_schedule 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_report_schedule 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_report_schedule. 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_report_schedule 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 →