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

gala_launchpad_list_bans

List all banned users for a token. Returns a paginated list of banned users with their ban details using cursor-based pagination. Supports filtering by search query, name, or user address. Filter Behavior: - search: Combined search on userAddress OR fullName (partial match) - name: Filter by full...

SERVERGala SOURCE@gala-chain/gala-mcp-server
Low RISK CLASS
Category Read
Parameters 61 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-list-bans.md

What gala_launchpad_list_bans does on Gala

AI agents call gala_launchpad_list_bans 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
name string — Filter by fullName only (case-insensitive, partial match).
cursor string — Cursor from previous response (omit for first page).
search string — Optional search query (fuzzy match filter)
pageSize integer — Results per page (default: 20, maximum: 100)
tokenName string Yes Token name.
userAddress string — Filter by userAddress only (case-insensitive, partial match).

Parameters from the server's own tool schema.

Why gala_launchpad_list_bans is rated Low

Even though gala_launchpad_list_bans 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 signalsAdmin/system-level operation

Questions about gala_launchpad_list_bans

What does the gala_launchpad_list_bans tool do? +

List all banned users for a token. Returns a paginated list of banned users with their ban details using cursor-based pagination. Supports filtering by search query, name, or user address. Filter Behavior: - search: Combined search on userAddress OR fullName (partial match) - name: Filter by fullName only - userAddress: Filter by userAddress only RETURNS: { bans: [...], pageInfo: { hasNextPage, endCursor, hasPreviousPage, startCursor } } Authentication: Requires streamAdminApiKey (admin) OR JWT auth (token owner). 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_list_bans accept? +

gala_launchpad_list_bans accepts 6 parameters: name, cursor, search, pageSize, tokenName, userAddress. 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_list_bans? +

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

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

Can I rate-limit gala_launchpad_list_bans? +

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

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

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

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