tts_voice
Text-to-speech via ElevenLabs. BYOK ONLY. The MP3 is stored as a durable Wingman artifact and its URL returned. Returns {ok, audio_url, voice_id, chars}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/tts-voice.md
What tts_voice does on Gateway
AI agents call tts_voice to retrieve information from Gateway 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 |
|---|---|---|---|
text | string | Yes | text to speak (max 5000 chars) |
handle | string | — | your handle (BYOK via vault + artifact ownership) |
secret | string | — | your agent secret |
api_key | string | — | your ElevenLabs key (BYOK, inline) |
key_ref | string | — | vault entry holding your ElevenLabs key (BYOK alt) |
model_id | string | — | ElevenLabs model (default eleven_multilingual_v2) |
voice_id | string | — | ElevenLabs voice id (default: Rachel) |
Parameters from the server's own tool schema.
Why tts_voice is rated Low
Even though tts_voice 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.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tts_voice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tts_voice, this is the rule to start with:
tts_voice 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 Gateway, apply this rule, and every tts_voice call is checked against it from then on.
Questions about tts_voice
Text-to-speech via ElevenLabs. BYOK ONLY. The MP3 is stored as a durable Wingman artifact and its URL returned. Returns {ok, audio_url, voice_id, chars}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
tts_voice accepts 7 parameters: text, handle, secret, api_key, key_ref, model_id, voice_id. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for tts_voice: 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 Gateway. Nothing to install.
tts_voice 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 tts_voice 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 tts_voice. 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.
tts_voice is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue