delete_huly_sequence
Permanently delete a never-used Sequence or CustomSequence resolved by exact sequence ID or attached class ID/name. expectedCurrentValue must be 0 and is an atomic compare-and-delete guard, so an active or advanced counter cannot be removed; referenced CustomSequence records are protected. ${SEQU...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-huly-sequence.md
What delete_huly_sequence does on Huly
AI agents call delete_huly_sequence 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_huly_sequence is rated Critical
This tool irreversibly deletes data (Sequence/CustomSequence records). While it includes safety guards (expectedCurrentValue check, protection for referenced/active sequences), the core operation is permanent deletion with no undo capability. This is the defining characteristic of the Destructive category, which takes precedence over Write operations.
From the tool's definition Tool name contains 'delete'; description explicitly states 'Permanently delete' and 'cannot be removed' with guards indicating irreversible data loss.
Attacks that exploit this kind of access
The rule that runs delete_huly_sequence 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_huly_sequence, this is the rule to start with:
delete_huly_sequence 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_huly_sequence call is checked against it from then on.
Questions about delete_huly_sequence
Permanently delete a never-used Sequence or CustomSequence resolved by exact sequence ID or attached class ID/name. expectedCurrentValue must be 0 and is an atomic compare-and-delete guard, so an active or advanced counter cannot be removed; referenced CustomSequence records are protected. ${SEQUENCE_WRITE_GUARD}. 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_huly_sequence: 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_huly_sequence 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_huly_sequence 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_huly_sequence. 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_huly_sequence 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