AI agents call list_voices to retrieve information from Portals without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
age | string | — | Filter by age bucket (e.g. 'young', 'middle_aged', 'old'). |
page | integer | — | Page index (0-based). Defaults to 0. |
accent | string | — | Filter by accent (e.g. 'american', 'british'). |
gender | string | — | Filter by gender (e.g. 'male', 'female'). |
search | string | — | Free-text search over voice names/descriptions. |
use_case | string | — | Filter by use case (e.g. 'narrative_story', 'characters'). |
Parameters from the server's own tool schema.
This tool retrieves a catalog of available voices from ElevenLabs without modifying, creating, deleting, or executing any operations. It is a straightforward read-only operation with minimal blast radius if misused by an AI agent—at worst it would retrieve voice metadata unnecessarily.
From the tool's definition Tool name 'list_voices' and description 'List available ElevenLabs voices' indicates data retrieval with no side effects. The mention of pagination and filters confirms this is a query operation.
Attacks that exploit this kind of access
List available ElevenLabs voices for text_to_speech. Results are paginated (100 per page). Use filters to narrow the catalog. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
list_voices accepts 6 parameters: age, page, accent, gender, search, use_case. The full parameter table on this page comes from the server's own tool schema.
Register the Portals 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 Portals. 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 Portals MCP server (portals-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_voices is one line of Portals's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →