get_status_category
Get one generic Huly StatusCategory by ID or exact case-insensitive label. Pass ofAttribute when a label exists for multiple status attributes; ambiguous labels are rejected with matching IDs.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-status-category.md
What get_status_category does on Huly
AI agents call get_status_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_status_category is rated Low
This tool queries and retrieves status category information by ID or label. It has no side effects, does not modify data, and does not execute external operations. It is a simple lookup/fetch operation, fitting the Read category definition.
From the tool's definition Tool description states it 'Get[s] one generic Huly StatusCategory by ID or exact case-insensitive label' — purely retrieval operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs get_status_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_status_category, this is the rule to start with:
get_status_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_status_category call is checked against it from then on.
Questions about get_status_category
Get one generic Huly StatusCategory by ID or exact case-insensitive label. Pass ofAttribute when a label exists for multiple status attributes; ambiguous labels are rejected with matching IDs. 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_status_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_status_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_status_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_status_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_status_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