gala_launchpad_on_token_ban_changed
Watch for token ban and unban events in real-time. Triggers when tokens are banned or unbanned by administrators. Includes: - TOKEN_BANNED: Token removed from trading/creation due to policy violation - TOKEN_UNBANNED: Ban lifted, token restored to normal status Returns: - tokenBansChanged: Number...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-on-token-ban-changed.md
What gala_launchpad_on_token_ban_changed does on Gala
AI agents call gala_launchpad_on_token_ban_changed 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
banStatus | string | — | Filter by ban status (optional). |
tokenName | string | Yes | Watch ban changes for this token (required). |
intervalMs | number | — | Poll interval in milliseconds (default: 30000 / 30 seconds). |
durationSeconds | number | — | How long to watch for new events in seconds (default: 60). |
Parameters from the server's own tool schema.
Why gala_launchpad_on_token_ban_changed is rated Low
Even though gala_launchpad_on_token_ban_changed 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs gala_launchpad_on_token_ban_changed 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_token_ban_changed, this is the rule to start with:
gala_launchpad_on_token_ban_changed is read-only, so it stays allowed. 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_on_token_ban_changed call is checked against it from then on.
Questions about gala_launchpad_on_token_ban_changed
Watch for token ban and unban events in real-time. Triggers when tokens are banned or unbanned by administrators. Includes: - TOKEN_BANNED: Token removed from trading/creation due to policy violation - TOKEN_UNBANNED: Ban lifted, token restored to normal status Returns: - tokenBansChanged: Number of ban status change events detected - events: Array of ban events with tokenName, newBanStatus, reason, and timestamp Filter Options: - tokenName: REQUIRED. Token bans are watched per-token; there is no way to watch every token at once. - banStatus: Filter by status ('BANNED' or 'UNBANNED'). It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_on_token_ban_changed accepts 4 parameters: banStatus, tokenName, intervalMs, durationSeconds. Required: tokenName. 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_on_token_ban_changed: 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_on_token_ban_changed is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gala_launchpad_on_token_ban_changed 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_on_token_ban_changed. 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_on_token_ban_changed 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