list_active_room_participants
List transient active virtual-office participants and positions, optionally filtered by roomId.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-active-room-participants.md
What list_active_room_participants does on Huly
AI agents call list_active_room_participants 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_active_room_participants is rated Low
This tool retrieves and queries participant data from virtual rooms without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with optional filtering capability, presenting minimal security risk.
From the tool's definition Tool name contains 'list' and description states 'List transient active virtual-office participants and positions' — a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_active_room_participants 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_active_room_participants, this is the rule to start with:
list_active_room_participants 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_active_room_participants call is checked against it from then on.
Questions about list_active_room_participants
List transient active virtual-office participants and positions, optionally filtered by roomId. 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_active_room_participants: 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_active_room_participants 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_active_room_participants 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_active_room_participants. 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_active_room_participants 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