complete_todo
Complete a Planner ToDo by setting doneOn. Huly may trim future work slots and run issue automation when the ToDo is attached to an issue.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/complete-todo.md
What complete_todo does on Huly
AI agents use complete_todo 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 complete_todo is rated Medium
This tool modifies data (marks a ToDo as completed) in a reversible manner—a user can uncomplete a ToDo later. While it mentions triggering automation workflows as side effects, the core capability is Write (updating doneOn state). It does not execute arbitrary code (Execute category), does not permanently delete anything (Destructive), and does not involve financial transactions (Financial).
From the tool's definition Tool description states it "Complete[s] a Planner ToDo by setting doneOn" and indicates it triggers secondary effects ("Huly may trim future work slots and run issue automation when the ToDo is attached to an issue").
Attacks that exploit this kind of access
The rule that runs complete_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 complete_todo, this is the rule to start with:
complete_todo 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 complete_todo call is checked against it from then on.
Questions about complete_todo
Complete a Planner ToDo by setting doneOn. Huly may trim future work slots and run issue automation when the ToDo is attached to an issue. 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 complete_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.
complete_todo 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 complete_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 complete_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.
complete_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.
This server
Across the catalogue