This record as markdown: /tools/adbutler/draft-delete-schedule.md
What draft_delete_schedule does on AdButler
AI agents call draft_delete_schedule to permanently remove resources in AdButler, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Draft schedule ID |
Parameters from the server's own tool schema.
Why draft_delete_schedule is rated Critical
The tool performs a deletion operation on a draft schedule, which cannot be undone. Although it targets a 'draft' (potentially lower user impact than a live schedule), deletion is permanent and destructive. The presence of sibling 'archive_*' tools on the same server suggests that destructive deletion is distinguished from reversible archiving, reinforcing that this tool is Destructive rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Delete a draft schedule' — this irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs draft_delete_schedule 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 draft_delete_schedule, this is the rule to start with:
draft_delete_schedule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every draft_delete_schedule call is checked against it from then on.
Questions about draft_delete_schedule
Delete a draft schedule. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
draft_delete_schedule accepts 1 parameter: id. Required: 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 draft_delete_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.
draft_delete_schedule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the draft_delete_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 draft_delete_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.
draft_delete_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.
More on AdButler, and thousands of servers like it.
Across the catalogue