list_space_permissions
List core Huly Permission records for space/workspace access control discovery. Filter by scope, objectClass, or search text. This is read-only and does not assign permissions.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-space-permissions.md
What list_space_permissions does on Huly
AI agents call list_space_permissions to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_space_permissions is rated Low
This tool queries permission metadata within a Huly workspace for discovery purposes. It performs no side effects—no creation, modification, deletion, or execution of external operations. The explicit 'read-only' designation and negation of permission assignment confirm this is a pure data retrieval function, fitting the Read category with low severity.
From the tool's definition Tool name: 'list_space_permissions'. Description explicitly states 'List core Huly Permission records' and 'This is read-only and does not assign permissions.' The operation retrieves and filters existing permission records without modifying or deleting them.
Attacks that exploit this kind of access
The rule that runs list_space_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 list_space_permissions, this is the rule to start with:
list_space_permissions is read-only, so it stays allowed. 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 list_space_permissions call is checked against it from then on.
Questions about list_space_permissions
List core Huly Permission records for space/workspace access control discovery. Filter by scope, objectClass, or search text. This is read-only and does not assign permissions. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_space_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.
list_space_permissions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_space_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 list_space_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.
list_space_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