gala_launchpad_pin_message
Pin a message to a token's chat. Only one message can be pinned per token at a time. Pinning a new message automatically unpins any previously pinned message. Authorization: - Token owner (JWT auth) - Moderator with MANAGER or MODERATOR role (JWT or API key) RETURNS: { success: true } Authenticat...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-pin-message.md
What gala_launchpad_pin_message does on Gala
AI agents use gala_launchpad_pin_message to create or update resources in Gala, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gala environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | ID of the message to pin. |
Parameters from the server's own tool schema.
Why gala_launchpad_pin_message is rated Medium
An AI agent can call gala_launchpad_pin_message faster than any human can review: one bad instruction and it creates or modifies resources in Gala by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs gala_launchpad_pin_message 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_pin_message, this is the rule to start with:
gala_launchpad_pin_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_pin_message call is checked against it from then on.
Questions about gala_launchpad_pin_message
Pin a message to a token's chat. Only one message can be pinned per token at a time. Pinning a new message automatically unpins any previously pinned message. Authorization: - Token owner (JWT auth) - Moderator with MANAGER or MODERATOR role (JWT or API key) RETURNS: { success: true } Authentication: Requires streamAdminApiKey (admin) OR JWT auth (token owner). It is categorised as a Write tool in the Gala MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gala_launchpad_pin_message accepts 1 parameter: id. Required: id. 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_pin_message: 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_pin_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gala_launchpad_pin_message 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_pin_message. 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_pin_message 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