gala_launchpad_monitor_global_feed_events_reference

Reference: Monitor and filter global feed events. IMPORTANT: The global feed is a CLIENT-SIDE feature in the SDK. This tool provides documentation. Event monitoring happens in your client code. Available Event Types Token Events (broadcast to all subscribers): - stream_status: Stream active/idle/disabled status changed - trade_executed: Buy/sell trade on bonding curve - holder_count_updated: Holder count increased/decreased - pool_badge_assigned: Pool earned a badge - viewer_count: Live viewer count updated - token_config_updated: Unified config change (countdown, language, toggles, social links) - stats_updated: Token stats update (price, market cap, bonding curve after trades) Site Config Events (global feature flags): - site_config_changed: Generic config change event - stream_global_status: Global streaming enabled/disabled - chat_global_status: Global chat enabled/disabled - comments_global_status: Global comments enabled/disabled - webhooks_global_status: Global webhooks enabled/disabled Monitoring Events launchpad-sdk's StreamWebSocketService calls one callback per event type, and serves any number of subscriptions on the one feed room (the SDK ships no React hooks for the feed: in React, keep the service and the events you buffer in component state). typescript import { StreamWebSocketService, getEnvironmentConfig } from '@gala-chain/launchpad-sdk'; const service = new StreamWebSocketService({ url: getEnvironmentConfig('prod').launchpadBaseUrl, }); const unsubscribe = service.subscribeToGlobalFeed({ onTradeExecuted: (data) => { console.log(Trade on ${data.tokenName}: ${data.tradeType}); }, onStreamStatus: (data) => { console.log(Stream status: ${data.status}); }, onViewerCount: (data) => { console.log(Viewers: ${data.viewerCount}); }, onTokenConfigUpdated: (data) => { console.log(Config updated for ${data.tokenName}); }, onStatsUpdated: (data) => { console.log(Stats: ${data.tokenName} price=${data.galaPrice}); }, onStreamGlobalStatus: (data) => { console.log(Streaming globally ${data.enabled ? 'enabled' : 'disabled'}); }, }); Client-Side Filtering The feed carries every token's events; filter them in your callbacks: typescript // Only process trades for visible tokens const visibleTokens = new Set(['bitcoin', 'ethereum']); // A second subscription is added next to the first: it replaces nothing service.subscribeToGlobalFeed({ onTradeExecuted: (data) => { if (visibleTokens.has(data.tokenName)) updateTokenCard(data); }, // Only one site config event onStreamGlobalStatus: (data) => updateGlobalUI(data), }); Use Cases 1. Homepage Card Updates: Monitor stream_status, trade_executed, viewer_count, holder_count, stats_updated 2. Real-Time Charts: Monitor stats_updated for price and volume data 3. Token Config Changes: Monitor token_config_updated for countdown, language, toggle changes 4. Feature Availability: Monitor site_config_changed events 5. Activity Feed: Buffer and display recent events to users 6. Analytics: Count and aggregate event types Best Practices - Buffer management: Keep the events you buffer bounded (100-1000 events) - Unsubscribe cleanup: Leave the feed when the component unmounts - Client-side filtering: Filter by tokenNames to reduce processing - Selective subscriptions: Only listen to event types you need - Error handling: Handle connection drops and reconnection Documentation In the launchpad-sdk source tree (not in the npm package): - Quick Start (5 min): docs/websocket/QUICKSTART.md - Complete Guide: docs/websocket/GLOBAL-FEED.md - Example: examples/global-feed-filtering-demo.ts Authentication: None required (public endpoint). It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.

Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_monitor_global_feed_events_reference: 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_monitor_global_feed_events_reference 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_monitor_global_feed_events_reference 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_monitor_global_feed_events_reference. 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_monitor_global_feed_events_reference 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.