gala_launchpad_explain_websocket_events
Get comprehensive documentation of all WebSocket events. Lists and explains all 35+ real-time WebSocket events available on the Launchpad platform, including: EVENT CATEGORIES: 1. Stream Events (STREAM_STATUS, RECORDING_STATUS, etc.) 2. Chat Events (STREAM_CHAT_SENT, CONTENT_REACTION_ADDED, etc.)...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-explain-websocket-events.md
What gala_launchpad_explain_websocket_events does on Gala
AI agents call gala_launchpad_explain_websocket_events 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 |
|---|---|---|---|
format | string | — | Output format (optional, default: full). |
category | string | — | Filter events by category (optional, default: all). |
Parameters from the server's own tool schema.
Why gala_launchpad_explain_websocket_events is rated Low
Even though gala_launchpad_explain_websocket_events 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.
Attacks that exploit this kind of access
The rule that runs gala_launchpad_explain_websocket_events 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_explain_websocket_events, this is the rule to start with:
gala_launchpad_explain_websocket_events 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_explain_websocket_events call is checked against it from then on.
Questions about gala_launchpad_explain_websocket_events
Get comprehensive documentation of all WebSocket events. Lists and explains all 35+ real-time WebSocket events available on the Launchpad platform, including: EVENT CATEGORIES: 1. Stream Events (STREAM_STATUS, RECORDING_STATUS, etc.) 2. Chat Events (STREAM_CHAT_SENT, CONTENT_REACTION_ADDED, etc.) 3. Trading Events (TRADE_EXECUTED) 4. Pool Events (POOL_METADATA_UPDATED, POOL_BADGE_ASSIGNED, HOLDER_COUNT_UPDATED, TOKEN_CONFIG_UPDATED) 5. Moderator Events (MODERATOR_ADDED, MODERATOR_REMOVED, MODERATOR_ROLE_UPDATED) 6. Moderation Events (USER_BANNED, USER_UNBANNED, BAN_ENFORCEMENT) 7. Ban Events (TOKEN_BANNED, TOKEN_UNBANNED) 8. Overseer Events (OVERSEER_ADDED, OVERSEER_REMOVED) 9. Comment Events (COMMENT_CREATED) 10. User Events (USER_PROFILE_UPDATED) 11. API Key Events (API_KEY_CREATED, API_KEY_UPDATED, API_KEY_REVOKED) 12. Platform Stats Events (STATS_UPDATED) For each event: - Description of what triggers it - Room scope (token-specific, global, user-specific) - Event payload structure - Example JSON - SDK subscription method - MCP watcher tool - Recommended filters Returns: Detailed documentation of all events with examples and usage patterns. It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_explain_websocket_events accepts 2 parameters: format, category. 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_explain_websocket_events: 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_explain_websocket_events 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_explain_websocket_events 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_explain_websocket_events. 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_explain_websocket_events 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