run_ffmpeg_command · FFmpeg MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_ffmpeg_command does on FFmpeg MCP Server

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

This tool executes external commands (FFmpeg) whose effects depend entirely on the arguments provided by an AI agent. While sandboxed, FFmpeg commands can perform various operations from simple transcoding to complex filters, metadata manipulation, and file I/O operations.

From the tool's definition Tool name 'run_ffmpeg_command' indicates execution of FFmpeg commands. Server description states it 'Enables secure video and audio processing using FFmpeg commands in an isolated sandbox environment,' confirming this tool runs arbitrary FFmpeg operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_ffmpeg_command Rate-limited

run_ffmpeg_command 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": {
    "run_ffmpeg_command": {
      "limits": [
        {
          "counter": "run_ffmpeg_command_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 run_ffmpeg_command

What does the run_ffmpeg_command tool do? +

run_ffmpeg_command. 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 run_ffmpeg_command? +

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

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

Can I rate-limit run_ffmpeg_command? +

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

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

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