get_todo
Get one Planner ToDo by raw todoId or by human locator such as issue + title + owner. Returns stable ToDo fields, owner, attachment context, description, labels count, and work slot count.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-todo.md
What get_todo does on Huly
AI agents call get_todo to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_todo is rated Low
This tool retrieves and queries existing ToDo data by identifier or human-readable locator. The 'Get' verb and 'Returns' language clearly indicate a read-only data retrieval operation with no side effects, matching the Read category definition. The blast radius of misuse is minimal—at worst, an agent could retrieve information it shouldn't have access to, but cannot modify or delete anything.
From the tool's definition Tool description explicitly states 'Get one Planner ToDo' and 'Returns' fields, indicating retrieval-only operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_todo, this is the rule to start with:
get_todo is read-only, so it stays allowed. 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 get_todo call is checked against it from then on.
Questions about get_todo
Get one Planner ToDo by raw todoId or by human locator such as issue + title + owner. Returns stable ToDo fields, owner, attachment context, description, labels count, and work slot count. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_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.
get_todo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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