Show or hide an HTML5 graphics overlay on a production
AI agents invoke wave_show_graphic to trigger actions in WAVE MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool controls real-time visual elements on a live production stream. It is not a simple data read or write; it executes an action that immediately affects what viewers see on an active stream. While not destructive or financial, it triggers an external operation with visible real-time consequences, placing it in the Execute category.
From the tool's definition 'Show or hide an HTML5 graphics overlay on a production' — triggers an external operation (displaying/removing a live overlay) on a running production
Attacks that exploit this kind of access
Show or hide an HTML5 graphics overlay on a production. It is categorised as a Execute tool in the WAVE MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WAVE MCP Server MCP server in PolicyLayer and add a rule for wave_show_graphic: 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_show_graphic is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wave_show_graphic 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_show_graphic. 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_show_graphic 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 →