Get real-time health metrics for a stream including bitrate, frame rate, and latency
AI agents call wave_get_stream_health 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 is a pure data retrieval operation that queries streaming health metrics. It performs no writes, deletions, code execution, or financial operations. The tool is used for observability and monitoring of stream status, which is a read-only operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name and description indicate it 'Get[s] real-time health metrics' for monitoring purposes only. Returns telemetry data (bitrate, frame rate, latency) with no modification or side effects.
Attacks that exploit this kind of access
Get real-time health metrics for a stream including bitrate, frame rate, and latency. 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_health: 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_health 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_health 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_health. 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_health 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 →