gala_launchpad_unsubscribe_from_global_feed_reference

Reference: Unsubscribe from the global feed. IMPORTANT: The global feed is a CLIENT-SIDE feature in the SDK. This tool provides documentation. Unsubscription happens in your client code. When to Unsubscribe Unsubscribe from the global feed when: - Component unmounts (React) - User navigates away - Feature is no longer needed - Application is shutting down - Connection is being closed Unsubscribing launchpad-sdk's StreamWebSocketService holds the subscription (the SDK ships no React hooks for the feed: in React, unsubscribe in your effect's cleanup). typescript import { StreamWebSocketService, getEnvironmentConfig } from '@gala-chain/launchpad-sdk'; const service = new StreamWebSocketService({ url: getEnvironmentConfig('prod').launchpadBaseUrl, }); // Every subscription returns its own unsubscribe. The feed room is left when the LAST one is released. const unsubscribe = service.subscribeToGlobalFeed({ onTradeExecuted: (event) => console.log('Trade:', event), onStreamStatus: (event) => console.log('Stream status:', event), }); // Later, when done with the feed unsubscribe(); console.log('Unsubscribed from global feed'); // And finally, close the connection service.disconnect(); console.log('Disconnected from WebSocket'); In React: typescript useEffect(() => { const unsubscribe = service.subscribeToGlobalFeed(callbacks); return unsubscribe; }, []); Cleanup Sequence Best practice cleanup sequence: typescript // 1. Unsubscribe from global feed (this subscription only) unsubscribe(); // 2. Remove what subscribeToStream registered for a token, if you used it service.unsubscribeFromStream('tokenName'); // 3. Disconnect WebSocket (releases every subscriber, listener and timer) service.disconnect(); Resource Management After unsubscribing: - This subscription's callbacks stop firing; other subscribers of the feed are untouched - The feed room is left once no subscriber needs it - Can still reconnect/resubscribe later if needed Errors and Edge Cases typescript // Safe to call multiple times: the room reference is released once unsubscribe(); unsubscribe(); // No error, no effect // Is any subscriber holding the feed room? service.isSubscribedToGlobalFeed(); // Disconnecting releases everything; the unsubscribe functions you hold stay harmless service.disconnect(); 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-demo.ts Authentication: None required (public endpoint). It is categorised as a Destructive tool in the Gala MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_unsubscribe_from_global_feed_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_unsubscribe_from_global_feed_reference is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Yes. Add a rate_limit block to the gala_launchpad_unsubscribe_from_global_feed_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_unsubscribe_from_global_feed_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_unsubscribe_from_global_feed_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.