set_space_role_members
Replace members assigned to one role on a typed Huly space while preserving all other role assignments. Role accepts a raw role _id or exact role name from the space
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-space-role-members.md
What set_space_role_members does on Huly
AI agents use set_space_role_members 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 set_space_role_members is rated Medium
This tool modifies access control by changing role memberships on a space, which can grant or revoke permissions for multiple users. While reversible, it affects authorization state and could inadvertently lock out users or grant inappropriate access if misused by an AI agent. Categorized as Write (reversible modification) rather than Execute (arbitrary code) or Destructive (irreversible deletion).
From the tool's definition Tool description states it 'Replace members assigned to one role' which modifies role assignments. The verb 'Replace' indicates mutation of existing state. This is a reversible modification (members can be reassigned), not deletion.
Attacks that exploit this kind of access
The rule that runs set_space_role_members 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 set_space_role_members, this is the rule to start with:
set_space_role_members 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 set_space_role_members call is checked against it from then on.
Questions about set_space_role_members
Replace members assigned to one role on a typed Huly space while preserving all other role assignments. Role accepts a raw role _id or exact role name from the space. 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 set_space_role_members: 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.
set_space_role_members 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 set_space_role_members 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 set_space_role_members. 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.
set_space_role_members 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