remove_space_role_members
Idempotently remove members from 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/remove-space-role-members.md
What remove_space_role_members does on Huly
AI agents call remove_space_role_members to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_space_role_members is rated Critical
Removing members from a role in a space revokes their access/membership, which is a destructive operation. While 'idempotently' suggests it's safe to repeat, the action itself (revoking role membership) is not easily reversible without knowing the prior state. The blast radius is high because misuse could lock out users from a space.
From the tool's definition 'remove members from one role on a typed Huly space' — removes members from a role, which is an irreversible deletion of access/membership assignment
Attacks that exploit this kind of access
The rule that runs remove_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 remove_space_role_members, this is the rule to start with:
remove_space_role_members is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every remove_space_role_members call is checked against it from then on.
Questions about remove_space_role_members
Idempotently remove members from 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 Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for remove_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.
remove_space_role_members is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue