list_workflow_statuses
List generic Huly workflow Status records across the workspace model. Filter by status attribute ID/exact name and category ID/exact label. Returns resolved attribute and category relationships. For one tracker project
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-workflow-statuses.md
What list_workflow_statuses does on Huly
AI agents call list_workflow_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_workflow_statuses is rated Low
This tool retrieves and filters workflow status records from a workspace model without creating, modifying, deleting, or executing any side effects. It returns resolved relationships but performs no mutations. The operation is a straightforward data query with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_workflow_statuses' and description 'List generic Huly workflow Status records' indicates data retrieval/query operation with no modification capability. Terms like 'list' and 'filter' confirm read-only functionality.
Attacks that exploit this kind of access
The rule that runs list_workflow_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_workflow_statuses, this is the rule to start with:
list_workflow_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_workflow_statuses call is checked against it from then on.
Questions about list_workflow_statuses
List generic Huly workflow Status records across the workspace model. Filter by status attribute ID/exact name and category ID/exact label. Returns resolved attribute and category relationships. For one tracker project. 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_workflow_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_workflow_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_workflow_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_workflow_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_workflow_statuses 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