create_schedule
Create a calendar schedule. Owner accepts an employee/person ID, exact name, or email; calendar can be targeted by calendarId or calendarName.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-schedule.md
What create_schedule does on Huly
AI agents use create_schedule to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why create_schedule is rated Medium
Creating a calendar schedule is a reversible write operation: schedules can be modified or deleted afterward. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because misconfigured schedules could affect team coordination, but impact is localized to calendar data and no critical system functions are compromised.
From the tool's definition Tool description states 'Create a calendar schedule' — a clear write operation that creates new data. The parameters (owner ID/name/email, calendarId/calendarName) are inputs for persistent calendar entry creation.
Attacks that exploit this kind of access
The rule that runs create_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_schedule, this is the rule to start with:
create_schedule stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every create_schedule call is checked against it from then on.
Questions about create_schedule
Create a calendar schedule. Owner accepts an employee/person ID, exact name, or email; calendar can be targeted by calendarId or calendarName. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly 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 Huly. 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 Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue