Get detailed performance metrics for a stream including bitrate, latency, quality scores, and error rates
AI agents call wave_get_stream_metrics to retrieve information from WAVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring and analytics data about stream performance without modifying, executing, or deleting anything. It is a straightforward read operation that queries existing metrics. The potential misuse is minimal—an AI agent could only view stream performance data, not affect it. Therefore, it poses a low security risk.
From the tool's definition The tool description explicitly states it 'Get[s] detailed performance metrics' including 'bitrate, latency, quality scores, and error rates'.
Attacks that exploit this kind of access
Get detailed performance metrics for a stream including bitrate, latency, quality scores, and error rates. It is categorised as a Read tool in the WAVE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WAVE MCP Server MCP server in PolicyLayer and add a rule for wave_get_stream_metrics: 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 WAVE MCP Server. Nothing to install.
wave_get_stream_metrics 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 wave_get_stream_metrics 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 wave_get_stream_metrics. 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.
wave_get_stream_metrics is provided by the WAVE MCP Server MCP server (wave-av/mcp-server). 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 →