Convert a two-speaker dialogue to speech using FlowSpeech. Assign Speaker1: and Speaker2: prefixes in the text.
AI agents invoke flowspeech_tts_multi to trigger actions in FlowSpeech MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external text-to-speech operation via the FlowSpeech API, generating audio output from input text. It executes an external service call whose effects (audio generation, potential API usage/billing) depend on the arguments provided.
From the tool's definition Convert a two-speaker dialogue to speech using FlowSpeech
Attacks that exploit this kind of access
Convert a two-speaker dialogue to speech using FlowSpeech. Assign Speaker1: and Speaker2: prefixes in the text. It is categorised as a Execute tool in the FlowSpeech MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FlowSpeech MCP Server MCP server in PolicyLayer and add a rule for flowspeech_tts_multi: 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 FlowSpeech MCP Server. Nothing to install.
flowspeech_tts_multi is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the flowspeech_tts_multi 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 flowspeech_tts_multi. 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.
flowspeech_tts_multi is provided by the FlowSpeech MCP Server MCP server (waeckerlinfederowicz66-sketch/mcp-flowspeech-server). 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 →