unschedule_todo
Remove ToDo work slots. Pass either workSlotId to remove one slot, locator with scope=all, or locator with scope=future and optional from.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/unschedule-todo.md
What unschedule_todo does on Huly
AI agents call unschedule_todo to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unschedule_todo is rated Critical
The tool explicitly removes ToDo work slots. While not catastrophic in blast radius (only affects scheduling entries), the removal of work slots is a destructive operation that cannot be undone, especially with scope=all which could remove all slots at once. The irreversible nature of deletion places this in the Destructive category.
From the tool's definition 'Remove ToDo work slots' - the operation removes/deletes scheduled work slots, which is an irreversible deletion of scheduling data
Attacks that exploit this kind of access
The rule that runs unschedule_todo 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 unschedule_todo, this is the rule to start with:
unschedule_todo 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 Huly, apply this rule, and every unschedule_todo call is checked against it from then on.
Questions about unschedule_todo
Remove ToDo work slots. Pass either workSlotId to remove one slot, locator with scope=all, or locator with scope=future and optional from. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for unschedule_todo: 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.
unschedule_todo 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 unschedule_todo 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 unschedule_todo. 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.
unschedule_todo 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.
Across the catalogue