add_space_role_members
Idempotently add members 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/add-space-role-members.md
What add_space_role_members does on Huly
AI agents use add_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 add_space_role_members is rated Medium
This tool creates or modifies role assignments for space members in Huly. It is a Write action because it adds members to roles (reversible role assignment changes) rather than permanently deleting data or executing arbitrary code. Severity is medium because incorrect role assignments could grant unintended access but are reversible through subsequent modifications.
From the tool's definition Tool name contains 'add_' verb and description states 'add members to one role' and 'preserving all other role assignments', indicating reversible modification of space membership roles.
Attacks that exploit this kind of access
The rule that runs add_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 add_space_role_members, this is the rule to start with:
add_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 add_space_role_members call is checked against it from then on.
Questions about add_space_role_members
Idempotently add members 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 add_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.
add_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 add_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 add_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.
add_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