list_statuses
List all issue statuses for a Huly project with category info. Returns status name, isDone, isCanceled, and isDefault flags. Use this to discover valid statuses before creating or updating issues.
This record as markdown: /tools/dugynoo-huly-mcp/list-statuses.md
What list_statuses does on Huly
AI agents call list_statuses 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 list_statuses is rated Low
This tool retrieves and queries existing status metadata from a Huly project. It has no side effects, creates no data, executes no operations, and performs no destructive actions. It is used to discover valid statuses before other operations, making it a straightforward Read category tool with low severity since misuse would only return information the agent could already discover through other means.
From the tool's definition Tool name is 'list_statuses' and description states it 'List all issue statuses' and 'Returns status name, isDone, isCanceled, and isDefault flags' — purely retrieval operations with no mutation of data.
Attacks that exploit this kind of access
The rule that runs list_statuses 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 list_statuses, this is the rule to start with:
list_statuses 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 list_statuses call is checked against it from then on.
Questions about list_statuses
List all issue statuses for a Huly project with category info. Returns status name, isDone, isCanceled, and isDefault flags. Use this to discover valid statuses before creating or updating issues. 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 list_statuses: 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.
list_statuses 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 list_statuses 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 list_statuses. 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.
list_statuses is provided by the Huly MCP server (dugynoo/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