gala_launchpad_get_connected_clients
List currently connected WebSocket clients with optional filtering. Returns a paginated list of connected WebSocket clients, with optional filters for room, token, user addresses, authentication status, and connection duration. Useful for monitoring active connections and targeting specific audie...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-get-connected-clients.md
What gala_launchpad_get_connected_clients does on Gala
AI agents call gala_launchpad_get_connected_clients to retrieve information from Gala without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
room | string | — | Optional room name filter (e.g., "token:anime"). |
limit | number | — | Page size (default: 25, max: 100). |
offset | integer | — | Pagination offset (default: 0). |
tokenName | string | — | Shorthand for room=token:{name}. |
isOverseer | boolean | — | Filter by admin/overseer status. |
userAddress | string | — | Find specific user (exact match). |
authenticated | boolean | — | Filter by authentication status. |
userAddresses | string | — | Comma-separated list of user addresses to find. |
minConnectionSeconds | integer | — | Only include clients connected longer than X seconds. |
Parameters from the server's own tool schema.
Why gala_launchpad_get_connected_clients is rated Low
Even though gala_launchpad_get_connected_clients only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs gala_launchpad_get_connected_clients safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gala, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gala_launchpad_get_connected_clients, this is the rule to start with:
gala_launchpad_get_connected_clients 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 Gala, apply this rule, and every gala_launchpad_get_connected_clients call is checked against it from then on.
Questions about gala_launchpad_get_connected_clients
List currently connected WebSocket clients with optional filtering. Returns a paginated list of connected WebSocket clients, with optional filters for room, token, user addresses, authentication status, and connection duration. Useful for monitoring active connections and targeting specific audiences. Query Parameters: - room: Filter by room name (e.g., "token:anime") - tokenName: Shorthand for room=token:{name} - userAddress: Find specific user (exact match) - userAddresses: Find any of these users (comma-separated) - authenticated: Filter by auth status - isOverseer: Filter by admin/overseer status - minConnectionSeconds: Only clients connected longer than X seconds - offset/limit: Pagination Connection Info Includes: - Socket ID - Wallet address (if authenticated) - Authentication status - Connected rooms (subscribed channels) - Connection duration - Last activity timestamp RETURNS: { clients: [ { socketId, address?, authenticated, connectedAt, lastActivity, rooms: [...] } ], summary: { totalConnected, authenticatedCount, anonymousCount, overseerCount, requestedUsersOnline, rooms: [{ room, connectedCount, authenticatedCount }, ...] }, pagination: { offset, limit, total, hasMore } } Authentication: Requires streamAdminApiKey (admin) OR JWT auth as Overseer. It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_get_connected_clients accepts 9 parameters: room, limit, offset, tokenName, isOverseer, userAddress, authenticated, userAddresses, minConnectionSeconds. The full parameter table on this page comes from the server's own tool schema.
Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_get_connected_clients: 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 Gala. Nothing to install.
gala_launchpad_get_connected_clients 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 gala_launchpad_get_connected_clients 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 gala_launchpad_get_connected_clients. 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.
gala_launchpad_get_connected_clients is provided by the Gala MCP server (@gala-chain/gala-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gala, and thousands of servers like it.
This server
Across the catalogue