wave_stop_stream · WAVE MCP Server MCP: Risk & Policy

WHAT IT DOES

What wave_stop_stream does on WAVE MCP Server

AI agents invoke wave_stop_stream 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.

WHY IT NEEDS A POLICY

Why wave_stop_stream needs a policy

This tool performs a real-time operational action that stops an active stream—a live broadcast with viewers and ongoing production activity. While the action is reversible (a new stream can be started), it has significant immediate consequences: it terminates service to active viewers, interrupts content delivery, and disrupts studio operations.

From the tool's definition Tool name 'wave_stop_stream' and description 'Stop an active stream by its ID' indicates the tool executes an action that triggers external operations (halting a live broadcast). The effect is immediate and dependent on the stream ID argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wave_stop_stream Rate-limited

wave_stop_stream stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wave_stop_stream": {
      "limits": [
        {
          "counter": "wave_stop_stream_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WAVE MCP Server, so you can run agents against it safely.

FAQ

Questions about wave_stop_stream

What does the wave_stop_stream tool do? +

Stop an active stream by its ID. 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.

How do I enforce a policy on wave_stop_stream? +

Register the WAVE MCP Server MCP server in PolicyLayer and add a rule for wave_stop_stream: 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.

What risk level is wave_stop_stream? +

wave_stop_stream is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wave_stop_stream? +

Yes. Add a rate_limit block to the wave_stop_stream 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.

How do I block wave_stop_stream completely? +

Set action: deny in the PolicyLayer policy for wave_stop_stream. 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.

What MCP server provides wave_stop_stream? +

wave_stop_stream 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.