update_huly_custom_sequence
Set only the prefix of a CustomSequence resolved by exact sequence ID or attached class ID/name. The compare-and-set guard does not change the counter and refuses a concurrent change; standard Sequence records are protected. ${SEQUENCE_WRITE_GUARD}
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-huly-custom-sequence.md
What update_huly_custom_sequence does on Huly
AI agents use update_huly_custom_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 update_huly_custom_sequence is rated Medium
This tool modifies data (updating a CustomSequence prefix) in a reversible manner. While it affects system configuration that could have downstream impacts, it is not destructive (no deletion), not execution of arbitrary code, and not financial. The compare-and-set pattern suggests careful coordination to prevent corruption.
From the tool's definition Tool description explicitly states "Set only the prefix of a CustomSequence" and mentions "compare-and-set guard" which indicates atomic, reversible modification. The action is to update a prefix field, not delete or execute arbitrary code.
Attacks that exploit this kind of access
The rule that runs update_huly_custom_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 update_huly_custom_sequence, this is the rule to start with:
update_huly_custom_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 update_huly_custom_sequence call is checked against it from then on.
Questions about update_huly_custom_sequence
Set only the prefix of a CustomSequence resolved by exact sequence ID or attached class ID/name. The compare-and-set guard does not change the counter and refuses a concurrent change; standard Sequence records are protected. ${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 update_huly_custom_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.
update_huly_custom_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 update_huly_custom_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 update_huly_custom_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.
update_huly_custom_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