delete_schedule_preset
Delete a saved schedule. Campaigns keep their own copy, so this never changes how an existing campaign sends.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/delete-schedule-preset.md
What delete_schedule_preset does on Max MCP Server
AI agents call delete_schedule_preset to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_schedule_preset is rated Critical
This tool permanently removes a schedule preset from the system. Although the description notes that existing campaigns retain their own copy and won't be affected, the deletion itself is irreversible—once deleted, the preset cannot be recovered without restoration from backup. This is a classic destructive operation.
From the tool's definition Tool name 'delete_schedule_preset' and description states it deletes 'a saved schedule'. The word 'Delete' combined with the irreversible nature of removing a preset configuration indicates a destructive operation.
Attacks that exploit this kind of access
The rule that runs delete_schedule_preset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_schedule_preset, this is the rule to start with:
delete_schedule_preset 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 Max MCP Server, apply this rule, and every delete_schedule_preset call is checked against it from then on.
Questions about delete_schedule_preset
Delete a saved schedule. Campaigns keep their own copy, so this never changes how an existing campaign sends. It is categorised as a Destructive tool in the Max MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for delete_schedule_preset: 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 Max MCP Server. Nothing to install.
delete_schedule_preset 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 delete_schedule_preset 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 delete_schedule_preset. 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.
delete_schedule_preset is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue