gala_launchpad_get_event_schema
Get detailed schema/interface for a specific WebSocket event. Returns TypeScript interface, JSON Schema validation, example payload, and documentation for any event. EVENTS AVAILABLE: Stream: STREAM_STATUS, RECORDING_STATUS, SIMULCAST_STATUS, DOWNLOAD_READY, STREAM_COUNTDOWN_UPDATED, STREAM_LANGU...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-get-event-schema.md
What gala_launchpad_get_event_schema does on Gala
AI agents call gala_launchpad_get_event_schema 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 | — | Format for the schema (optional, default: both). |
eventName | string | Yes | The name of the event (e.g., TRADE_EXECUTED, STREAM_STATUS, MODERATOR_ADDED). |
includeExample | boolean | — | Include example payload (optional, default: true). |
Parameters from the server's own tool schema.
Why gala_launchpad_get_event_schema is rated Low
Even though gala_launchpad_get_event_schema 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_get_event_schema 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_event_schema, this is the rule to start with:
gala_launchpad_get_event_schema 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_event_schema call is checked against it from then on.
Questions about gala_launchpad_get_event_schema
Get detailed schema/interface for a specific WebSocket event. Returns TypeScript interface, JSON Schema validation, example payload, and documentation for any event. EVENTS AVAILABLE: Stream: STREAM_STATUS, RECORDING_STATUS, SIMULCAST_STATUS, DOWNLOAD_READY, STREAM_COUNTDOWN_UPDATED, STREAM_LANGUAGE_UPDATED Chat: STREAM_CHAT_SENT, STREAM_CHAT_DELETED, STREAM_CHAT_PINNED, STREAM_CHAT_UNPINNED, CHAT_STATUS_CHANGED, STREAM_CONTROL_STATUS_CHANGED, CONTENT_REACTION_ADDED, CONTENT_REACTION_REMOVED, USER_TYPING, CONTENT_FLAGGED, FLAG_RESOLVED Trading: TRADE_EXECUTED Pool: POOL_METADATA_UPDATED, POOL_SOCIAL_LINKS_UPDATED, POOL_BADGE_ASSIGNED, HOLDER_COUNT_UPDATED, TOKEN_CONFIG_UPDATED Moderation: MODERATOR_ADDED, MODERATOR_REMOVED, MODERATOR_ROLE_UPDATED, USER_BANNED, USER_UNBANNED, BAN_ENFORCEMENT Ban: TOKEN_BANNED, TOKEN_UNBANNED Overseer: OVERSEER_ADDED, OVERSEER_REMOVED Comment: COMMENT_CREATED User: USER_PROFILE_UPDATED API Key: API_KEY_CREATED, API_KEY_UPDATED, API_KEY_REVOKED Platform Stats: STATS_UPDATED Returns: - TypeScript interface - JSON Schema - Example payload (minimum + full) - Room scope (which room(s) this event is emitted to) - Subscription method name - Description and use cases. It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_get_event_schema accepts 3 parameters: format, eventName, includeExample. Required: eventName. 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_event_schema: 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_event_schema 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_event_schema 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_event_schema. 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_event_schema 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