update_tag_category
Update a tag/label category. Accepts category ID or label name. Only provided fields are modified.
This record as markdown: /tools/dugynoo-huly-mcp/update-tag-category.md
What update_tag_category does on Huly
AI agents use update_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 update_tag_category is rated Medium
This tool modifies metadata (tag/label category properties) within a project management system. It is categorized as Write because it creates or modifies data reversibly. Severity is medium because misuse could corrupt project organization structures and metadata, affecting team workflows, but the impact is limited to a single category and is reversible through subsequent updates.
From the tool's definition Tool name 'update_tag_category' and description 'Update a tag/label category' indicates modification of existing data. The phrase 'Only provided fields are modified' confirms this is a reversible update operation, not a deletion or destruction.
Attacks that exploit this kind of access
The rule that runs update_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 update_tag_category, this is the rule to start with:
update_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 update_tag_category call is checked against it from then on.
Questions about update_tag_category
Update a tag/label category. Accepts category ID or label name. Only provided fields are modified. 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 update_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.
update_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 update_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 update_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.
update_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