list_spaces
List generic Huly spaces across modules. When includeArchived is omitted, includeArchived=${DEFAULT_INCLUDE_ARCHIVED}. Returns raw space id, class, type, privacy, archived, autoJoin, member count, and owner count so module-specific tools can reuse the result.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-spaces.md
What list_spaces does on Huly
AI agents call list_spaces 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_spaces is rated Low
This is a query/retrieval operation that reads space metadata from Huly without creating, modifying, deleting, or executing any operations. The optional 'includeArchived' parameter is a filter flag for read operations, not an action trigger. No irreversible changes, financial transactions, or code execution are involved.
From the tool's definition Tool name 'list_spaces' and description 'List generic Huly spaces' indicates data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs list_spaces 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_spaces, this is the rule to start with:
list_spaces 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_spaces call is checked against it from then on.
Questions about list_spaces
List generic Huly spaces across modules. When includeArchived is omitted, includeArchived=${DEFAULT_INCLUDE_ARCHIVED}. Returns raw space id, class, type, privacy, archived, autoJoin, member count, and owner count so module-specific tools can reuse the result. 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_spaces: 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_spaces 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_spaces 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_spaces. 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_spaces 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