gala_launchpad_global_feed_status_reference
Reference: Check global feed subscription status. IMPORTANT: The global feed is a CLIENT-SIDE feature in the SDK. This tool provides documentation. Status checking happens in your client code. Checking Subscription Status launchpad-sdk's StreamWebSocketService holds the feed connection (the SDK s...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-global-feed-status-reference.md
What gala_launchpad_global_feed_status_reference does on Gala
AI agents call gala_launchpad_global_feed_status_reference 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.
Why gala_launchpad_global_feed_status_reference is rated Low
Even though gala_launchpad_global_feed_status_reference 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_global_feed_status_reference 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_global_feed_status_reference, this is the rule to start with:
gala_launchpad_global_feed_status_reference 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_global_feed_status_reference call is checked against it from then on.
Questions about gala_launchpad_global_feed_status_reference
Reference: Check global feed subscription status. IMPORTANT: The global feed is a CLIENT-SIDE feature in the SDK. This tool provides documentation. Status checking happens in your client code. Checking Subscription Status launchpad-sdk's StreamWebSocketService holds the feed connection (the SDK ships no React hooks for it: in React, keep the service in your component state). typescript import { StreamWebSocketService, getEnvironmentConfig } from '@gala-chain/launchpad-sdk'; const service = new StreamWebSocketService({ url: getEnvironmentConfig('prod').launchpadBaseUrl, }); const unsubscribe = service.subscribeToGlobalFeed(); const isSubscribed = service.isSubscribedToGlobalFeed(); const isConnected = service.isConnected(); console.log(Subscription status: ${isSubscribed ? 'subscribed' : 'not subscribed'}); console.log(Connection status: ${isConnected ? 'connected' : 'disconnected'}); Status Indicators - isSubscribed: true while at least one subscriber holds the global:feed room - isConnected: true if WebSocket connection is active and authenticated Common Status Scenarios | Subscribed | Connected | Meaning | |-----------|-----------|---------| | false | false | Not initialized - subscribeToGlobalFeed() registers and opens the socket | | true | false | Subscribed but connection dropped - reconnecting automatically, the feed is joined again on reconnect | | false | true | Connected but no subscriber holds the feed - call subscribeToGlobalFeed() | | true | true | ✅ Ready to receive events | 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 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_global_feed_status_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_global_feed_status_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_global_feed_status_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_global_feed_status_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_global_feed_status_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.
More on Gala, and thousands of servers like it.
This server
Across the catalogue