Create a new schedule for a Switcher device
AI agents use create_schedule to create or update resources in Switcher MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Switcher MCP Server environment.
This tool creates a new schedule, which is a reversible write operation. It modifies device configuration but can be undone via delete_schedule (a sibling tool). While scheduling automation of a switch could indirectly affect physical device operations, the create_schedule action itself is fundamentally a data creation operation.
From the tool's definition Tool name 'create_schedule' and description 'Create a new schedule for a Switcher device' indicate data creation. The tool creates a new schedule object/record in the device configuration.
Attacks that exploit this kind of access
Create a new schedule for a Switcher device. It is categorised as a Write tool in the Switcher MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Switcher MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_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_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_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_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 →