Delete a schedule from a Switcher device
AI agents call delete_schedule to permanently remove resources in Switcher MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_schedule tool performs an irreversible deletion operation on device schedules. Once deleted, the schedule cannot be recovered without manual recreation. This matches the Destructive category definition of 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because unauthorized deletion of automation schedules could disrupt home automation workflows, though the…
From the tool's definition Tool name contains 'delete' and description states 'Delete a schedule from a Switcher device' — this irreversibly removes data (a schedule configuration) from the device.
Attacks that exploit this kind of access
Delete a schedule from a Switcher device. It is categorised as a Destructive tool in the Switcher MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Switcher MCP Server MCP server in PolicyLayer and add a rule for 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 Switcher MCP Server. Nothing to install.
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 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 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.
delete_schedule is provided by the Switcher MCP Server MCP server (liebstein/switcher-mcp). 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 →