create_task_type
Add a Huly issue/task type to a project type idempotently by normalized name. Copies required workflow configuration from an existing template task type unless templateTaskType is supplied. Returns created, IDs, affected task type IDs, and a workspace-level workflow warning.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-task-type.md
What create_task_type does on Huly
AI agents use create_task_type 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_task_type is rated Medium
This tool creates and modifies data structures (task types and their workflow configurations) within Huly, which is a reversible Write operation. While it affects project structure, there is no indication it executes arbitrary code (Execute), deletes data (Destructive), or moves money (Financial). The 'idempotently' behavior suggests safe repetition.
From the tool's definition Tool description states 'Add a Huly issue/task type' and 'creates' a task type (as implied by 'create_' prefix). The operation is reversible and does not delete or execute arbitrary code.
Attacks that exploit this kind of access
The rule that runs create_task_type 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 create_task_type, this is the rule to start with:
create_task_type 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 create_task_type call is checked against it from then on.
Questions about create_task_type
Add a Huly issue/task type to a project type idempotently by normalized name. Copies required workflow configuration from an existing template task type unless templateTaskType is supplied. Returns created, IDs, affected task type IDs, and a workspace-level workflow warning. 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 create_task_type: 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.
create_task_type 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 create_task_type 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 create_task_type. 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.
create_task_type 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