set_global_space_admins
Replace the workspace-wide Huly space-admin list. Admins accept account UUIDs, exact emails, or exact person display names; pass admins=[] to clear the role. The tool resolves the stable core all-spaces space and Admin role internally.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-global-space-admins.md
What set_global_space_admins does on Huly
AI agents use set_global_space_admins 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_global_space_admins is rated Medium
This tool modifies the set of workspace administrators by replacing the admin list. While changes to administrative roles are sensitive and could enable further harm, the operation itself is reversible (admins can be re-added), making it Write rather than Destructive.
From the tool's definition Tool description states: 'Replace the workspace-wide Huly space-admin list' and 'pass admins=[] to clear the role'. The verb 'replace' indicates modification of access control settings.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs set_global_space_admins 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_global_space_admins, this is the rule to start with:
set_global_space_admins 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_global_space_admins call is checked against it from then on.
Questions about set_global_space_admins
Replace the workspace-wide Huly space-admin list. Admins accept account UUIDs, exact emails, or exact person display names; pass admins=[] to clear the role. The tool resolves the stable core all-spaces space and Admin role internally. 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_global_space_admins: 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_global_space_admins 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_global_space_admins 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_global_space_admins. 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_global_space_admins 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