update_huly_attribute
Update label, index, automation-only, or hidden state for a Huly Attribute resolved by ID or exact name. Pass class by ID/name to disambiguate. Built-in attributes permit hidden-only updates; all other built-in mutations are protected, and property keys/types cannot be changed here. Hide/unhide u...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-huly-attribute.md
What update_huly_attribute does on Huly
AI agents use update_huly_attribute 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_attribute is rated Medium
This tool creates or modifies attribute metadata reversibly within Huly. While it updates state (label, index, flags), these changes are not irreversible deletions and can be reverted by subsequent updates. The tool does not delete data, execute arbitrary code, or trigger financial operations. The scope is limited to attribute configuration within a single system.
From the tool's definition Tool description explicitly states it performs 'Update' operations on attributes including 'label, index, automation-only, or hidden state'. The phrase 'Update' and modification of attribute properties are characteristic of Write operations.
Attacks that exploit this kind of access
The rule that runs update_huly_attribute 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_attribute, this is the rule to start with:
update_huly_attribute 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_attribute call is checked against it from then on.
Questions about update_huly_attribute
Update label, index, automation-only, or hidden state for a Huly Attribute resolved by ID or exact name. Pass class by ID/name to disambiguate. Built-in attributes permit hidden-only updates; all other built-in mutations are protected, and property keys/types cannot be changed here. Hide/unhide uses the SDK behavior exercised by Huly settings. ${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 update_huly_attribute: 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_attribute 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_attribute 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_attribute. 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_attribute 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