List all streams in your WAVE account with pagination support
AI agents call wave_list_streams 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 performs a data retrieval operation (list/query) with no side effects. It allows viewing existing streams but cannot create, modify, delete, or execute operations. The pagination support confirms it is a standard read operation. Severity is low because listing streams poses minimal risk—the worst case is information disclosure about account streams, which is low-impact.
From the tool's definition Tool name 'wave_list_streams' and description 'List all streams in your WAVE account with pagination support' indicate a query operation that retrieves stream information without modifying or executing actions.
Attacks that exploit this kind of access
List all streams in your WAVE account with pagination support. 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_list_streams: 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_list_streams 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_list_streams 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_list_streams. 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_list_streams 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 →