gala_launchpad_get_available_roles

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

Low RISK CLASS

Category Read

Parameters 00 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-get-available-roles.md

WHAT IT DOES

What gala_launchpad_get_available_roles does on Gala

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

RISK

Why gala_launchpad_get_available_roles is rated Low

Even though gala_launchpad_get_available_roles 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gala_launchpad_get_available_roles Allowed

gala_launchpad_get_available_roles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gala_launchpad_get_available_roles": {}
  }
}

ALLOW ONLY 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_get_available_roles call is checked against it from then on.

FAQ

Questions about gala_launchpad_get_available_roles

What does the gala_launchpad_get_available_roles tool do? +

Get all available roles and permissions for token delegation. Returns reference data about the role system, including: - All available roles (OWNER, MANAGER, TECHNICAL_PRODUCER, MODERATOR) - Role descriptions and hierarchy levels - Permissions assigned to each role - Complete list of all available permissions Role Hierarchy (highest to lowest): - OWNER (level 3): Full access to all token operations - MANAGER (level 2): Full moderator + tech producer + recordings + settings - TECHNICAL_PRODUCER (level 1): Stream setup and management - MODERATOR (level 0): Community and chat management Available Permissions: - MANAGE_COMMENTS: Create/delete comments - MANAGE_CHAT: Send/delete chat messages - BAN_USERS: Ban users from token streams - UNBAN_USERS: Remove bans from users - MANAGE_SIMULCAST: Add/remove simulcast targets - GET_STREAM_KEY: View the stream key - STOP_STREAM: Stop an active stream - RESET_STREAM_KEY: Generate a new stream key - START_STREAM: Start a new stream - DELETE_RECORDINGS: Delete stream recordings - MANAGE_STREAM_SETTINGS: Update stream settings (countdown, language) This is static reference data - it doesn't change per user or token. Useful for building role selection UIs and understanding permission hierarchies. RETURNS: { roles: [...], permissions: [...] } Authentication: None required (public endpoint). It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gala_launchpad_get_available_roles? +

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

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

Can I rate-limit gala_launchpad_get_available_roles? +

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

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

gala_launchpad_get_available_roles 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →