create_huly_enum
Create a Huly model enum with ordered option values. An exact case-insensitive name is idempotent only when its ordered values match; otherwise the call returns a conflict. ${MODEL_WRITE_GUARD}
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-huly-enum.md
What create_huly_enum does on Huly
AI agents use create_huly_enum 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_enum is rated Medium
The tool creates new enum definitions in the Huly system, which is a Write operation (creates/modifies data reversibly). It is not destructive because enums with matching names/values are idempotent, and the guard suggests safeguards exist. Severity is medium because misconfiguration of model enums could disrupt system functionality but would be fixable. The operation is not Execute/Destructive/Financial/Read.
From the tool's definition Tool description explicitly states 'Create a Huly model enum' with the action of establishing 'ordered option values'. The mention of '${MODEL_WRITE_GUARD}' indicates protective measures are in place.
Attacks that exploit this kind of access
The rule that runs create_huly_enum 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_enum, this is the rule to start with:
create_huly_enum 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_enum call is checked against it from then on.
Questions about create_huly_enum
Create a Huly model enum with ordered option values. An exact case-insensitive name is idempotent only when its ordered values match; otherwise the call returns a conflict. ${MODEL_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_enum: 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_enum 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_enum 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_enum. 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_enum 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