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

gala_launchpad_on_holder_count_changed

Watch for token holder count changes in real-time. Triggers whenever the holder count for a token changes, including: - New holders making their first purchase - Holders liquidating their entire position - Changes in holder distribution and tiers Returns: - holdersChanged: Number of holder count ...

SERVERGala SOURCE@gala-chain/gala-mcp-server
Low RISK CLASS
Category Read
Parameters 41 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-on-holder-count-changed.md

What gala_launchpad_on_holder_count_changed does on Gala

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

ParameterTypeRequiredDescription
tokenName string Yes Watch holder changes for this token (required).
intervalMs number — Poll interval in milliseconds (default: 30000 / 30 seconds).
minThreshold number — Only notify if holder count changes by at least this amount (optional).
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_holder_count_changed is rated Low

Even though gala_launchpad_on_holder_count_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

Questions about gala_launchpad_on_holder_count_changed

What does the gala_launchpad_on_holder_count_changed tool do? +

Watch for token holder count changes in real-time. Triggers whenever the holder count for a token changes, including: - New holders making their first purchase - Holders liquidating their entire position - Changes in holder distribution and tiers Returns: - holdersChanged: Number of holder count change events detected - events: Array of holder count events with tokenName, newCount, previousCount, and timestamp Filter Options: - tokenName: REQUIRED. Holder-count changes are watched per-token; there is no way to watch every token at once. - minThreshold: Only notify if holder count changes by >= minThreshold. 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_on_holder_count_changed accept? +

gala_launchpad_on_holder_count_changed accepts 4 parameters: tokenName, intervalMs, minThreshold, 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_holder_count_changed? +

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

What risk level is gala_launchpad_on_holder_count_changed? +

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

Can I rate-limit gala_launchpad_on_holder_count_changed? +

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

How do I block gala_launchpad_on_holder_count_changed completely? +

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

What MCP server provides gala_launchpad_on_holder_count_changed? +

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

Across the catalogue

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