create_huly_permission
Create a base Huly Permission with a clear human label and optional class/transaction constraints. Class accepts an exact class ID, tail name, or label. Exact labels are idempotent only when the full definition matches. ${SECURITY_WRITE_GUARD}
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-huly-permission.md
What create_huly_permission does on Huly
AI agents use create_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 create_huly_permission is rated Medium
This tool creates permissions in a Huly instance, which modifies access control configuration. While reversible (Write rather than Destructive), creating or altering permissions is high-severity due to the blast radius: misconfigured permissions could grant unintended access to sensitive data or operations.
From the tool's definition Tool description states 'Create a base Huly Permission' with 'class/transaction constraints' and mentions idempotency conditions when 'full definition matches'.
Attacks that exploit this kind of access
The rule that runs create_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 create_huly_permission, this is the rule to start with:
create_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 create_huly_permission call is checked against it from then on.
Questions about create_huly_permission
Create a base Huly Permission with a clear human label and optional class/transaction constraints. Class accepts an exact class ID, tail name, or label. Exact labels are idempotent only when the full definition matches. ${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 create_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.
create_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 create_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 create_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.
create_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