Stateful voice conversation with context retention
AI agents invoke voice_chat to trigger actions in Voice-AGI 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.
The tool facilitates a stateful, multi-turn voice conversation that can trigger tool execution, memory management, and research operations. Since it can invoke other tools and external operations depending on conversational inputs, it falls under Execute.
From the tool's definition 'Stateful voice conversation with context retention' combined with server description stating it 'enables users to execute tools, manage memory, and conduct research through natural multi-turn dialogue'
Attacks that exploit this kind of access
Stateful voice conversation with context retention. It is categorised as a Execute tool in the Voice-AGI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Voice-AGI MCP Server MCP server in PolicyLayer and add a rule for voice_chat: 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-AGI MCP Server. Nothing to install.
voice_chat 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 voice_chat 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_chat. 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_chat is provided by the Voice-AGI MCP Server MCP server (marc-shade/voice-agi-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 →