List all available audio voices for text-to-speech generation
AI agents call listAudioVoices to retrieve information from Pollinations Think MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves metadata about available audio voices. There is no data modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal — an agent could only enumerate voice options, which is informational only.
From the tool's definition Tool name and description indicate it 'List[s] all available audio voices' — a retrieval operation with no side effects, modifications, or execution of external commands. It queries a list of static configuration data.
Attacks that exploit this kind of access
List all available audio voices for text-to-speech generation. It is categorised as a Read tool in the Pollinations Think MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pollinations Think MCP Server MCP server in PolicyLayer and add a rule for listAudioVoices: 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 Pollinations Think MCP Server. Nothing to install.
listAudioVoices 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 listAudioVoices 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 listAudioVoices. 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.
listAudioVoices is provided by the Pollinations Think MCP Server MCP server (palolxx/pollinations-think-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 →