list_voices
AI agents call list_voices to retrieve information from MiniMax MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_voices' operation retrieves or enumerates voice data without modification, creation, or deletion. No side effects or state changes are implied. This is a straightforward Read operation for discovering available resources. Confidence is not higher due to the empty description, but the name provides sufficient clarity in the MiniMax voice API context.
From the tool's definition Tool name 'list_voices' indicates a retrieval/query operation that lists available voices. The description is empty, but the naming convention and semantic context (sibling to voice_clone, voice_design, text_to_audio) strongly suggest this is a…
Attacks that exploit this kind of access
list_voices. It is categorised as a Read tool in the MiniMax MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MiniMax MCP Server MCP server in PolicyLayer and add a rule for list_voices: 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 MiniMax MCP Server. Nothing to install.
list_voices 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 list_voices 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 list_voices. 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.
list_voices is provided by the MiniMax MCP Server MCP server (minimax-ai/minimax-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →