Get voice pipeline statistics and latency metrics
AI agents call get_voice_stats to retrieve information from Voice-AGI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves observational data about system performance (statistics and latency). It has no side effects, does not modify state, execute code, delete data, or affect financial systems. It is a straightforward monitoring/diagnostic read operation.
From the tool's definition The tool 'get_voice_stats' retrieves 'voice pipeline statistics and latency metrics' with no indication of modification, deletion, or execution capabilities. The verb 'Get' and the nature of metrics retrieval align with data querying.
Attacks that exploit this kind of access
Get voice pipeline statistics and latency metrics. It is categorised as a Read tool in the Voice-AGI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Voice-AGI MCP Server MCP server in PolicyLayer and add a rule for get_voice_stats: 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.
get_voice_stats 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 get_voice_stats 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 get_voice_stats. 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.
get_voice_stats 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 →