create_huly_sequence
Create a zero-valued standard Sequence or prefixed CustomSequence for a class resolved by exact ID, tail name, or label. Retrying returns the matching existing definition and never resets or increments its counter; a different kind or prefix returns a conflict. ${SEQUENCE_WRITE_GUARD}
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-huly-sequence.md
What create_huly_sequence does on Huly
AI agents use create_huly_sequence 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_huly_sequence is rated Medium
This tool creates and potentially modifies sequence definitions in Huly, which are used for ID generation and tracking. These are data structures that can be created, queried, and potentially updated, making it a Write operation. It is not Execute (doesn't run arbitrary code), Destructive (doesn't irreversibly delete data—sequences can be recreated), or Financial.
From the tool's definition Tool name includes 'create' which creates a new sequence definition. Description states it creates 'a zero-valued standard Sequence or prefixed CustomSequence' and 'Retrying returns the matching existing definition', indicating reversible…
Attacks that exploit this kind of access
The rule that runs create_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 create_huly_sequence, this is the rule to start with:
create_huly_sequence 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_huly_sequence call is checked against it from then on.
Questions about create_huly_sequence
Create a zero-valued standard Sequence or prefixed CustomSequence for a class resolved by exact ID, tail name, or label. Retrying returns the matching existing definition and never resets or increments its counter; a different kind or prefix returns a conflict. ${SEQUENCE_WRITE_GUARD}. 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_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.
create_huly_sequence 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_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 create_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.
create_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.
This server
Across the catalogue