update_inventory_category
Rename and/or move an inventory category. category accepts ID or exact name; pass parentCategory when a name may be duplicated. Rejects duplicate names in the destination parent and self/descendant moves.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-inventory-category.md
What update_inventory_category does on Huly
AI agents use update_inventory_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_inventory_category is rated Medium
This tool creates or modifies data reversibly—it renames categories and changes their hierarchy (parentCategory). These are Write operations because they alter structure and naming without deletion. The safeguards mentioned (rejects duplicate names and invalid moves) indicate design control.
From the tool's definition Tool description states 'Rename and/or move an inventory category', which are reversible modification operations. The tool modifies (updates) category metadata without destroying data.
Attacks that exploit this kind of access
The rule that runs update_inventory_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_inventory_category, this is the rule to start with:
update_inventory_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_inventory_category call is checked against it from then on.
Questions about update_inventory_category
Rename and/or move an inventory category. category accepts ID or exact name; pass parentCategory when a name may be duplicated. Rejects duplicate names in the destination parent and self/descendant moves. 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_inventory_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_inventory_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_inventory_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_inventory_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_inventory_category 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