AI agents use create_report_schedule to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
frequency | string | — | Schedule frequency |
recipients | array | — | Array of recipient objects |
report_config_id | number | Yes | Report configuration ID |
Parameters from the server's own tool schema.
This tool creates a new report schedule, which is a reversible write operation—schedules can be modified or deleted later. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misconfigured report schedules could affect business reporting and analytics pipelines, but the impact is limited to scheduling configuration, not live campaigns or financial transactions.
From the tool's definition Tool name 'create_report_schedule' and description 'Create a new report schedule' indicate creation of a new configuration object.
Attacks that exploit this kind of access
Create a new report schedule. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_report_schedule accepts 3 parameters: frequency, recipients, 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 create_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.
create_report_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →