Check the status of all voice services including TTS, STT, LiveKit, and audio devices. IMPORTANT: Only use this tool for debugging when voice services fail. The system has automatic failover, so try using services directly first. This tool is for troubleshooting only. Provides a unified view of t...
AI agents call voice_status to retrieve information from Voice Mode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and reports the current state of voice services (TTS, STT, LiveKit, audio devices). It has no side effects—it does not create, modify, delete, or execute operations. The debugging use case mentioned in the description confirms it is passive information retrieval. No other services are triggered or modified by checking status.
From the tool's definition Tool name 'voice_status' and description 'Check the status of all voice services' indicates a read-only operation that retrieves status information.
Documented attack patterns abuse exactly the kind of access voice_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Voice Mode, and nothing reaches the server without passing your rules. This is the rule we recommend for voice_status:
{
"version": "1",
"default": "deny",
"tools": {
"voice_status": {}
}
}voice_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of all voice services including TTS, STT, LiveKit, and audio devices. IMPORTANT: Only use this tool for debugging when voice services fail. The system has automatic failover, so try using services directly first. This tool is for troubleshooting only. Provides a unified view of the voice infrastructure configuration and health. It is categorised as a Read tool in the Voice Mode MCP Server, which means it retrieves data without modifying state.
Register the Voice Mode MCP server in PolicyLayer and add a rule for voice_status: 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 Mode. Nothing to install.
voice_status 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 voice_status 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 voice_status. 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.
voice_status is provided by the Voice Mode MCP server (mbailey/voicemode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Voice Mode, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Voice Mode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.