create_space_role
Create a Huly role definition using a SpaceType ID or exact name and permission ID or exact label values. The call creates both the attached Role and required typed-space assignment attribute, compensating if the second write fails. Workspace-scoped permissions are restricted to the stable all-sp...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-space-role.md
What create_space_role does on Huly
AI agents use create_space_role 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_space_role is rated Medium
This is a Write operation because it creates new roles and permission assignments in the workspace. Severity is high because role creation directly impacts access control and authorization across the Huly system. An AI agent misusing this could create overprivileged roles or assign inappropriate permissions to users, affecting workspace security.
From the tool's definition Tool description explicitly states 'The call creates both the attached Role and required typed-space assignment attribute', confirming data creation. Key phrases: 'Create a Huly role definition', 'creates', 'write fails'.
Attacks that exploit this kind of access
The rule that runs create_space_role 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_space_role, this is the rule to start with:
create_space_role 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_space_role call is checked against it from then on.
Questions about create_space_role
Create a Huly role definition using a SpaceType ID or exact name and permission ID or exact label values. The call creates both the attached Role and required typed-space assignment attribute, compensating if the second write fails. Workspace-scoped permissions are restricted to the stable all-spaces SpaceType. Existing exact role names are idempotent only when permission sets match. ${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_space_role: 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_space_role 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_space_role 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_space_role. 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_space_role 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