gala_launchpad_on_pool_updated

SERVERGala SOURCE@gala-chain/gala-mcp-server

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-on-pool-updated.md

WHAT IT DOES

What gala_launchpad_on_pool_updated does on Gala

AI agents use gala_launchpad_on_pool_updated 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
`tokenName`	string	Yes	Watch updates for this token (required).
`intervalMs`	number	—	Poll interval in milliseconds (default: 30000 / 30 seconds).
`updateType`	string	—	Filter by update type (optional).
`durationSeconds`	number	—	How long to watch for new events in seconds (default: 60).

Parameters from the server's own tool schema.

RISK

Why gala_launchpad_on_pool_updated is rated Medium

An AI agent can call gala_launchpad_on_pool_updated 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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gala_launchpad_on_pool_updated 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_on_pool_updated, this is the rule to start with:

gala_launchpad_on_pool_updated Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gala_launchpad_on_pool_updated": {
      "limits": [
        {
          "counter": "gala_launchpad_on_pool_updated_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gala, apply this rule, and every gala_launchpad_on_pool_updated call is checked against it from then on.

FAQ

Questions about gala_launchpad_on_pool_updated

What does the gala_launchpad_on_pool_updated tool do? +

Watch for pool metadata updates in real-time. Triggers when pool metadata, social links, or badges are updated. Includes: - POOL_METADATA_UPDATED: Name, description, image, category changes - POOL_SOCIAL_LINKS_UPDATED: Website, Discord, Twitter, etc. changes - POOL_BADGE_ASSIGNED: New badges or badge assignments Returns: - poolsUpdated: Number of pool updates detected - updates: Array of pool update events with tokenName, updateType, and metadata changes Filter Options: - tokenName: REQUIRED. Pool updates are watched per-token; there is no way to watch every token at once. - updateType: Filter by type ('METADATA', 'SOCIAL_LINKS', or 'BADGE_ASSIGNED'). 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.

What parameters does gala_launchpad_on_pool_updated accept? +

gala_launchpad_on_pool_updated accepts 4 parameters: tokenName, intervalMs, updateType, durationSeconds. Required: tokenName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gala_launchpad_on_pool_updated? +

Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_on_pool_updated: 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_on_pool_updated? +

gala_launchpad_on_pool_updated is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gala_launchpad_on_pool_updated? +

Yes. Add a rate_limit block to the gala_launchpad_on_pool_updated 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_on_pool_updated completely? +

Set action: deny in the PolicyLayer policy for gala_launchpad_on_pool_updated. 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_on_pool_updated? +

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

KEEP EXPLORING

More on Gala, and thousands of servers like it.

This server

All 324 Gala tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →