This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-space-role-permissions.md
What set_space_role_permissions does on Huly
AI agents use set_space_role_permissions 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_permissions is rated Medium
The tool modifies role definitions (a reversible Write operation) rather than deleting them. However, the blast radius is high because changing role permissions in a space affects access control for potentially many users, which could grant or revoke significant privileges. This is Write rather than Destructive because the change is reversible and the original role can be restored.
From the tool's definition Tool name and description: 'set_space_role_permissions' which 'Replace one existing role definition' — this modifies an existing role's permissions configuration.
Attacks that exploit this kind of access
The rule that runs set_space_role_permissions 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_permissions, this is the rule to start with:
set_space_role_permissions 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_permissions call is checked against it from then on.
Questions about set_space_role_permissions
Replace one existing role definition. 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_permissions: 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_permissions 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_permissions 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_permissions. 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_permissions 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