create_sandbox · FFmpeg MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_sandbox does on FFmpeg MCP Server

AI agents invoke create_sandbox to trigger actions in FFmpeg 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 create_sandbox needs a policy

Creating a sandbox environment sets up an execution context for running FFmpeg commands. This is an infrastructure/environment provisioning action that enables subsequent command execution. While not immediately destructive, it establishes an isolated runtime environment whose purpose is to execute media processing commands.

From the tool's definition Creates a sandboxed environment for running ffmpeg commands

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_sandbox Rate-limited

create_sandbox 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": {
    "create_sandbox": {
      "limits": [
        {
          "counter": "create_sandbox_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 FFmpeg MCP Server, so you can run agents against it safely.

FAQ

Questions about create_sandbox

What does the create_sandbox tool do? +

Creates a sandboxed environment for running ffmpeg commands. It is categorised as a Execute tool in the FFmpeg 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 create_sandbox? +

Register the FFmpeg MCP Server MCP server in PolicyLayer and add a rule for create_sandbox: 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 FFmpeg MCP Server. Nothing to install.

What risk level is create_sandbox? +

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

Can I rate-limit create_sandbox? +

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

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

create_sandbox is provided by the FFmpeg MCP Server MCP server (radzevich/ffmpeg_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.