get_inventory_category
Get one inventory category by ID or exact name. If the name is duplicated under different parents, pass parentCategory or use the category ID.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-inventory-category.md
What get_inventory_category does on Huly
AI agents call get_inventory_category to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_inventory_category is rated Low
This tool queries and retrieves inventory category information without side effects. It is a straightforward read operation that does not modify, create, delete, or execute any external operations. The severity is low because unauthorized access to category metadata poses minimal risk.
From the tool's definition Tool performs a retrieval operation ('Get one inventory category') with no modification, creation, or deletion of data. The parameters indicate querying by ID or name lookup.
Attacks that exploit this kind of access
The rule that runs get_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 get_inventory_category, this is the rule to start with:
get_inventory_category is read-only, so it stays allowed. 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 get_inventory_category call is checked against it from then on.
Questions about get_inventory_category
Get one inventory category by ID or exact name. If the name is duplicated under different parents, pass parentCategory or use the category ID. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_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.
get_inventory_category is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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