wave_create_production · WAVE MCP Server MCP: Risk & Policy

WHAT IT DOES

What wave_create_production does on WAVE MCP Server

AI agents use wave_create_production to create or update resources in WAVE MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WAVE MCP Server environment.

WHY IT NEEDS A POLICY

Why wave_create_production needs a policy

This tool creates a new production resource, which is a reversible operation (productions can typically be deleted or modified). It does not execute arbitrary code, delete data, or commit financial obligations. It modifies the production environment by adding a new production.

From the tool's definition Tool name 'wave_create_production' and description 'Create a new studio production' indicate creation of new data/resources. The context shows this is part of a streaming API that manages studio productions, streams, and associated infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wave_create_production Rate-limited

wave_create_production stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_create_production": {
      "limits": [
        {
          "counter": "wave_create_production_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_create_production

What does the wave_create_production tool do? +

Create a new studio production with multi-camera support. It is categorised as a Write tool in the WAVE MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wave_create_production? +

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

wave_create_production is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wave_create_production? +

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

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

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