New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_workflow_status

Create a generic Huly workflow Status for an attribute resolved by ID or exact name. Optionally resolve a shared category by ID or exact label; pass a category ID when its label is ambiguous. Idempotently returns the existing normalized name in that attribute with created=false. Tracker project-t...

SERVERHuly SOURCE@firfi/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-workflow-status.md

What create_workflow_status does on Huly

AI agents use create_workflow_status 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 create_workflow_status is rated Medium

This tool creates new workflow status objects within Huly, which is a reversible modification of the system's workflow configuration. The idempotent behavior (returning existing records without duplication) and lack of data deletion or financial operations place it in the Write category rather than Execute or Destructive.

From the tool's definition Tool name 'create_workflow_status' and description states it will 'Create a generic Huly workflow Status' and 'Idempotently returns the existing normalized name in that attribute with created=false', indicating creation of new workflow status records.

Questions about create_workflow_status

What does the create_workflow_status tool do? +

Create a generic Huly workflow Status for an attribute resolved by ID or exact name. Optionally resolve a shared category by ID or exact label; pass a category ID when its label is ambiguous. Idempotently returns the existing normalized name in that attribute with created=false. Tracker project-type wiring remains owned by create_issue_status. 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.

How do I enforce a policy on create_workflow_status? +

Register the Huly MCP server in PolicyLayer and add a rule for create_workflow_status: 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.

What risk level is create_workflow_status? +

create_workflow_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_workflow_status? +

Yes. Add a rate_limit block to the create_workflow_status 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.

How do I block create_workflow_status completely? +

Set action: deny in the PolicyLayer policy for create_workflow_status. 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.

What MCP server provides create_workflow_status? +

create_workflow_status 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.