List all studio productions in your WAVE account
AI agents call wave_list_productions 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 and enumerates existing production data from the user's WAVE account. It performs a query-like operation that reads information without creating, modifying, deleting, executing code, or incurring financial obligations. The blast radius of misuse is minimal—an agent listing productions cannot harm systems, leak sensitive data at scale, or cause irreversible changes.
From the tool's definition Tool name includes 'list' and description states 'List all studio productions' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all studio productions in your WAVE account. 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_productions: 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_productions 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_productions 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_productions. 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_productions 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 →