update_huly_permission
Update a custom Huly Permission resolved by exact ID or exact label. Namespaced built-in permissions are protected. Label/description changes are allowed on unreferenced custom permissions; semantic changes are refused while referenced by a role or SpaceType descriptor. Null clears optional const...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-huly-permission.md
What update_huly_permission does on Huly
AI agents use update_huly_permission 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_permission is rated Medium
This tool modifies permission settings and constraints through reversible updates. While permissions control access (making this security-sensitive), the tool itself performs Write operations—updating labels, descriptions, and constraints on custom permissions. The presence of SECURITY_WRITE_GUARD suggests the server implements protective measures.
From the tool's definition Tool name contains 'update' and description explicitly states 'Update a custom Huly Permission' with operations like 'Label/description changes are allowed'. The description confirms reversible modifications to permission configurations.
Attacks that exploit this kind of access
The rule that runs update_huly_permission 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_permission, this is the rule to start with:
update_huly_permission 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_permission call is checked against it from then on.
Questions about update_huly_permission
Update a custom Huly Permission resolved by exact ID or exact label. Namespaced built-in permissions are protected. Label/description changes are allowed on unreferenced custom permissions; semantic changes are refused while referenced by a role or SpaceType descriptor. Null clears optional constraints. ${SECURITY_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_permission: 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_permission 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_permission 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_permission. 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_permission 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