gala_launchpad_remove_content_reaction
Remove a reaction from a pool message. Requires JWT or API key authentication. Only the user who created the reaction can remove it. RETURNS: { success: true } Authentication: Requires JWT session (call sdk.login() first).
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-remove-content-reaction.md
What gala_launchpad_remove_content_reaction does on Gala
AI agents call gala_launchpad_remove_content_reaction to permanently remove resources in Gala, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
messageId | string | Yes | Message ID in format msg-{timestamp}-{uuid} or chat-{timestamp}-{uuid} (supports both modern and legacy formats). |
tokenName | string | — | Token name. |
reactionType | string | Yes | Type of reaction: heart, fire, laugh, wow, or thumbs_up. |
Parameters from the server's own tool schema.
Why gala_launchpad_remove_content_reaction is rated Critical
An AI agent that decides to call gala_launchpad_remove_content_reaction doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Gala is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs gala_launchpad_remove_content_reaction 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_remove_content_reaction, this is the rule to start with:
gala_launchpad_remove_content_reaction is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gala, apply this rule, and every gala_launchpad_remove_content_reaction call is checked against it from then on.
Questions about gala_launchpad_remove_content_reaction
Remove a reaction from a pool message. Requires JWT or API key authentication. Only the user who created the reaction can remove it. RETURNS: { success: true } Authentication: Requires JWT session (call sdk.login() first). 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.
gala_launchpad_remove_content_reaction accepts 3 parameters: messageId, tokenName, reactionType. Required: messageId, reactionType. The full parameter table on this page comes from the server's own tool schema.
Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_remove_content_reaction: 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_remove_content_reaction 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_remove_content_reaction 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_remove_content_reaction. 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_remove_content_reaction 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.
Across the catalogue