AI agents use update_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 |
schedule_id | number | Yes | Schedule ID |
report_config_id | number | Yes | Report configuration ID |
Parameters from the server's own tool schema.
This tool modifies report scheduling configuration reversibly—changes can be undone by updating again to different parameters. It does not delete data (which would be Destructive), execute arbitrary code (which would be Execute), or move money (Financial). It falls squarely into Write category.
From the tool's definition Tool name 'update_report_schedule' and description 'Update a report schedule' indicate modification of existing configuration data. The term 'update' is a clear write operation that changes report scheduling parameters.
Attacks that exploit this kind of access
Update a 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.
update_report_schedule accepts 4 parameters: frequency, recipients, 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 update_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.
update_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 update_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 update_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.
update_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 →