delete_status_category
Permanently delete an unreferenced generic StatusCategory by ID or exact label. Refuses deletion while any Status references the category, preventing dangling relationships.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-status-category.md
What delete_status_category does on Huly
AI agents call delete_status_category to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_status_category is rated Critical
This tool irreversibly deletes data (StatusCategory records) from the Huly system. While it includes a safeguard (refusing deletion if Status objects reference it), deletion is the core destructive action and cannot be undone. This is more severe than Write (which is reversible) and falls squarely into Destructive category.
From the tool's definition 'Permanently delete an unreferenced generic StatusCategory by ID' - the word 'delete' combined with 'permanently' indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_status_category, this is the rule to start with:
delete_status_category is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_status_category call is checked against it from then on.
Questions about delete_status_category
Permanently delete an unreferenced generic StatusCategory by ID or exact label. Refuses deletion while any Status references the category, preventing dangling relationships. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for delete_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.
delete_status_category is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue