AI agents invoke speak_and_listen to trigger actions in Voice MCP. 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 both produces audio output and captures audio input in sequence, triggering external hardware operations (speaker and microphone). It goes beyond a simple read or write, as it executes a multi-step interaction with external systems (local Whisper STT and Supertonic TTS).
From the tool's definition 'Speak text aloud then immediately listen for a full response' — triggers both audio output (TTS) and audio input (STT) operations as a combined external interaction
Attacks that exploit this kind of access
Speak text aloud then immediately listen for a full response. It is categorised as a Execute tool in the Voice MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Voice MCP server in PolicyLayer and add a rule for speak_and_listen: 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 MCP. Nothing to install.
speak_and_listen 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_and_listen 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_and_listen. 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_and_listen is provided by the Voice MCP server (jochiang/voice-mcp). 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 →