list_voices
List available TTS voices (id, label, preview audio URL) for a provider: "minimax" (default engine) or "elevenlabs". Match the project's voice_tts_provider (see get_project) so picked ids work with its engine.
This record as markdown: /tools/com-framesail-framesail/list-voices.md
What list_voices does on Framesail
AI agents call list_voices to retrieve information from Framesail without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
provider | string | — | TTS engine to list voices for: "minimax" (default engine) or "elevenlabs"; match the project's voice_tts_provider |
Parameters from the server's own tool schema.
Why list_voices is rated Low
This is a straightforward read-only operation that lists voices from a TTS provider. It has no side effects on the system, project state, or any generated content. The worst-case misuse scenario is an agent iterating through voices unnecessarily, which has minimal blast radius.
From the tool's definition Tool "list_voices" retrieves and queries available TTS voice options with descriptive metadata (id, label, preview audio URL). No data is created, modified, deleted, or executed—it purely enumerates and returns information.
Attacks that exploit this kind of access
The rule that runs list_voices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_voices, this is the rule to start with:
list_voices is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every list_voices call is checked against it from then on.
Questions about list_voices
List available TTS voices (id, label, preview audio URL) for a provider: "minimax" (default engine) or "elevenlabs". Match the project's voice_tts_provider (see get_project) so picked ids work with its engine. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
list_voices accepts 1 parameter: provider. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail 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 Framesail. 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 Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue