Speak text aloud using the configured TTS engine.
AI agents invoke speak to trigger actions in Voice Bridge. 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 executes an action on the host system (producing audio output), which constitutes an external side-effect beyond simple data read/write. An AI agent could misuse it to produce unwanted or disruptive audio output. It falls under Execute as it triggers an external operation whose effects depend on the input text argument.
From the tool's definition "Speak text aloud" — triggers an external audio output operation on the host system using a TTS engine
Attacks that exploit this kind of access
Speak text aloud using the configured TTS engine. It is categorised as a Execute tool in the Voice Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Voice Bridge MCP server in PolicyLayer and add a rule for speak: 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 Voice Bridge. Nothing to install.
speak 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 speak 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 speak. 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.
speak is provided by the Voice Bridge MCP server (Tomorrow-You/voice-bridge). 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 →