Get current viewer count and viewer demographics for a stream or across all streams
AI agents call wave_get_viewers 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 analytics data (viewer count and demographics) without modifying, deleting, or triggering any actions. It is a read-only query operation. The severity is low because exposure of this data poses minimal risk—viewer metrics are typically non-sensitive operational analytics. Even if an AI agent calls this repeatedly, no harm results.
From the tool's definition Tool name 'wave_get_viewers' and description 'Get current viewer count and viewer demographics for a stream or across all streams' indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
Get current viewer count and viewer demographics for a stream or across all streams. 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_viewers: 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_viewers 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_viewers 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_viewers. 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_viewers 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 →