New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_schedule

Update a calendar schedule. Supports owner, title, description, duration, interval, availability, timeZone, and calendar move by calendarId or calendarName.

SERVERHuly SOURCE@firfi/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-schedule.md

What update_schedule does on Huly

AI agents use update_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 update_schedule is rated Medium

This tool creates or modifies data (calendar schedule attributes) in a reversible manner. The operation updates calendar metadata rather than executing external code or triggering irreversible deletions. While it could affect multiple calendar properties and potentially impact scheduling visibility, the changes are reversible through subsequent updates.

From the tool's definition Tool description explicitly states 'Update a calendar schedule' with modifiable fields including owner, title, description, duration, interval, availability, timeZone, and calendar move operations.

Questions about update_schedule

What does the update_schedule tool do? +

Update a calendar schedule. Supports owner, title, description, duration, interval, availability, timeZone, and calendar move 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.

How do I enforce a policy on update_schedule? +

Register the Huly MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_schedule? +

update_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_schedule? +

Yes. Add a rate_limit block to the update_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.

How do I block update_schedule completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_schedule? +

update_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.