wave_switch_camera · WAVE MCP Server MCP: Risk & Policy

WHAT IT DOES

What wave_switch_camera does on WAVE MCP Server

AI agents invoke wave_switch_camera 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_switch_camera needs a policy

This tool triggers an external real-time operation that changes what is broadcast to live viewers. It is not merely writing data to a store — it controls live production output, which has immediate, audience-visible effects. This fits Execute (triggering external operations whose effects depend on arguments).

From the tool's definition Switch the live program output to a different camera/source in a Cloud Switcher session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wave_switch_camera Rate-limited

wave_switch_camera 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_switch_camera": {
      "limits": [
        {
          "counter": "wave_switch_camera_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_switch_camera

What does the wave_switch_camera tool do? +

Switch the live program output to a different camera/source in a Cloud Switcher session. 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_switch_camera? +

Register the WAVE MCP Server MCP server in PolicyLayer and add a rule for wave_switch_camera: 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_switch_camera? +

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

Can I rate-limit wave_switch_camera? +

Yes. Add a rate_limit block to the wave_switch_camera 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_switch_camera completely? +

Set action: deny in the PolicyLayer policy for wave_switch_camera. 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_switch_camera? +

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