create_inventory_category
Create an inventory category. Defaults parentCategory to the Inventory root. Rejects duplicate category names under the same parent.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-inventory-category.md
What create_inventory_category does on Huly
AI agents use create_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 create_inventory_category is rated Medium
This tool creates new data (an inventory category) in a reversible manner. Creating a category can be undone by deletion. The blast radius is medium because creating duplicate or unwanted inventory categories could clutter the system and require manual cleanup, but it does not permanently destroy data or execute arbitrary code. It falls clearly under Write rather than Execute or Destructive.
From the tool's definition The tool 'create_inventory_category' explicitly 'Create[s]' a category. The description confirms it creates a new inventory category with a default parent and validates uniqueness constraints.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs create_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 create_inventory_category, this is the rule to start with:
create_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 create_inventory_category call is checked against it from then on.
Questions about create_inventory_category
Create an inventory category. Defaults parentCategory to the Inventory root. Rejects duplicate category names under the same parent. 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_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.
create_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 create_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 create_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.
create_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