create_tag_category
Create a new tag/label category. Idempotent: returns existing category if one with the same label and targetClass already exists (created=false). Defaults targetClass to tracker issues.
This record as markdown: /tools/dugynoo-huly-mcp/create-tag-category.md
What create_tag_category does on Huly
AI agents use create_tag_category 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_tag_category is rated Medium
This tool creates new metadata (tag/label categories) in the project management system. It is a Write operation because it creates new data structures that can be modified or deleted later. The severity is low because tag categories are organizational metadata with minimal blast radius—misuse would only clutter the category namespace and would not affect core project data, user access, or financial operations.
From the tool's definition Tool name "create_tag_category" and description explicitly states it "Create[s] a new tag/label category". The idempotent behavior (returns existing category if already exists) confirms this is a reversible creation operation, not destructive.
Attacks that exploit this kind of access
The rule that runs create_tag_category 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_tag_category, this is the rule to start with:
create_tag_category 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_tag_category call is checked against it from then on.
Questions about create_tag_category
Create a new tag/label category. Idempotent: returns existing category if one with the same label and targetClass already exists (created=false). Defaults targetClass to tracker issues. 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_tag_category: 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_tag_category 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_tag_category 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_tag_category. 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_tag_category 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