New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gala_launchpad_emit_feature_status

Emit a feature status changed event. Broadcasts globally that a feature's availability has changed (e.g., streaming disabled, trading paused, chat maintenance). Notifies all connected clients when features are disabled/enabled with optional recovery time. Event Recipients: All globally connected ...

SERVERGala SOURCE@gala-chain/gala-mcp-server
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-emit-feature-status.md

What gala_launchpad_emit_feature_status does on Gala

AI agents call gala_launchpad_emit_feature_status 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.

ParameterTypeRequiredDescription
reason string — Optional reason for the status change (e.g., "Service degradation", "Scheduled maintenance", "High load").
enabled boolean Yes Whether the feature is enabled (true) or disabled (false).
feature string Yes Feature name being toggled (e.g., "streaming", "trading", "chat", "nft_minting").
nextLiveStreamAt string — Optional ISO 8601 timestamp indicating when the feature will come back online (if disabled).

Parameters from the server's own tool schema.

Why gala_launchpad_emit_feature_status is rated Low

Even though gala_launchpad_emit_feature_status 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.

Risk signalsAdmin/system-level operation

Questions about gala_launchpad_emit_feature_status

What does the gala_launchpad_emit_feature_status tool do? +

Emit a feature status changed event. Broadcasts globally that a feature's availability has changed (e.g., streaming disabled, trading paused, chat maintenance). Notifies all connected clients when features are disabled/enabled with optional recovery time. Event Recipients: All globally connected clients (broadcast) RETURNS: { success: true, message: "Feature status event emitted" } Authentication: Requires streamAdminApiKey (admin) OR JWT auth as Overseer. It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.

What parameters does gala_launchpad_emit_feature_status accept? +

gala_launchpad_emit_feature_status accepts 4 parameters: reason, enabled, feature, nextLiveStreamAt. Required: enabled, feature. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gala_launchpad_emit_feature_status? +

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

What risk level is gala_launchpad_emit_feature_status? +

gala_launchpad_emit_feature_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gala_launchpad_emit_feature_status? +

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

How do I block gala_launchpad_emit_feature_status completely? +

Set action: deny in the PolicyLayer policy for gala_launchpad_emit_feature_status. 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.

What MCP server provides gala_launchpad_emit_feature_status? +

gala_launchpad_emit_feature_status 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gala's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.