gala_launchpad_site_config_state_reference
Reference: Access site configuration state from global feed. IMPORTANT: The global feed is a CLIENT-SIDE feature in the SDK. This tool provides documentation. Config access happens in your client code. Site Configuration Events The global feed broadcasts site-wide configuration changes. Track the...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-site-config-state-reference.md
What gala_launchpad_site_config_state_reference does on Gala
AI agents invoke gala_launchpad_site_config_state_reference to trigger actions in Gala. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why gala_launchpad_site_config_state_reference is rated High
gala_launchpad_site_config_state_reference triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs gala_launchpad_site_config_state_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_site_config_state_reference, this is the rule to start with:
gala_launchpad_site_config_state_reference stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_site_config_state_reference call is checked against it from then on.
Questions about gala_launchpad_site_config_state_reference
Reference: Access site configuration state from global feed. IMPORTANT: The global feed is a CLIENT-SIDE feature in the SDK. This tool provides documentation. Config access happens in your client code. Site Configuration Events The global feed broadcasts site-wide configuration changes. Track these to know when: - Streaming is globally enabled/disabled - Chat is globally enabled/disabled - Comments are globally enabled/disabled - Webhooks are globally enabled/disabled Accessing Config State launchpad-sdk's StreamWebSocketService delivers the config events and keeps the latest value of each switch: service.getSiteConfigState() returns { chatEnabled, streamingEnabled, commentsEnabled, webhooksEnabled, aiModerationEnabled } (undefined for a switch no event has announced since the feed was joined). The SDK ships no React hooks; in React, read the state in your own component state. typescript import { StreamWebSocketService, getEnvironmentConfig } from '@gala-chain/launchpad-sdk'; const service = new StreamWebSocketService({ url: getEnvironmentConfig('prod').launchpadBaseUrl, }); const unsubscribe = service.subscribeToGlobalFeed({ onSiteConfigChanged: (event) => { console.log('Site config changed:', event.key, event.value); }, onStreamGlobalStatus: (data) => { console.log('Stream status changed:', data.enabled); }, onStreamChatGlobalStatus: (data) => { console.log('Chat status changed:', data.enabled); }, onCommentsGlobalStatus: (data) => { console.log('Comments status changed:', data.enabled); }, onWebhooksGlobalStatus: (data) => { console.log('Webhooks status changed:', data.enabled); }, }); Event Payloads (launchpad-sdk types) typescript interface SiteConfigChangedEvent { // onSiteConfigChanged key: string; value: boolean | string; timestamp?: number; } interface FeatureGlobalStatusEvent { // onStreamGlobalStatus, onStreamChatGlobalStatus, ... enabled: boolean; timestamp?: number; } Events - site_config_changed: Generic config change (includes all flags) - stream_global_status: Streaming enabled/disabled globally - chat_global_status: Chat enabled/disabled globally - comments_global_status: Comments enabled/disabled globally - webhooks_global_status: Webhooks enabled/disabled globally Use Cases 1. Disable UI features: If streaming is disabled, don't show stream controls 2. Show status messages: Inform users when features are globally unavailable 3. Enable/disable monitoring: Only set up detailed monitoring if features are enabled 4. Real-time notifications: Notify users when features become available/unavailable 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 - Examples: examples/site-config-demo.ts Authentication: None required (public endpoint). It is categorised as a Execute tool in the Gala MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_site_config_state_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_site_config_state_reference is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gala_launchpad_site_config_state_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_site_config_state_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_site_config_state_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