// SCAN REPORT

FFmpeg MCP Tool

10 tools. 8 can modify or destroy data without limits.

8 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

8 can modify or destroy data

2 read-only

10 tools total

Community server · catalogue entry verified 04/07/2026

How to control FFmpeg MCP Tool ↓

TOOL MAP

What FFmpeg MCP Tool exposes to your agents

Read (2) Write / Execute (8) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous FFmpeg MCP Tool tools

Write · Medium batch_compress_images This tool writes/modifies data by compressing images in batch. Write · Medium batch_compress_videos This tool compresses videos in batch, which is a reversible write operation that modifies file data. Write · Medium compress_image Image compression is a reversible modification operation — the original file can be recovered or a new compressed version created without permanent data loss. Write · Medium compress_video Compressing a video file creates or overwrites output data.

8 of FFmpeg MCP Tool's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control FFmpeg MCP Tool

PolicyLayer is an MCP gateway — it sits between your AI agents and FFmpeg MCP Tool, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "batch_compress_images": {
    "limits": [
      {
        "counter": "batch_compress_images_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_ffmpeg_status": {
    "limits": [
      {
        "counter": "check_ffmpeg_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register FFmpeg MCP Tool — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FFMPEG MCP TOOL →

Instant setup, no code required.

FULL CATALOGUE

All 10 FFmpeg MCP Tool tools

WRITE 8 tools

Write batch_compress_images 批量压缩指定文件夹中的所有图片 Write batch_compress_videos 批量压缩指定文件夹中的所有视频 Write compress_image 压缩单个图片文件 Write compress_video 压缩单个视频文件 Write convert_image_format 转换图片格式 Write convert_video_format 转换视频格式 Write resize_image 调整图片尺寸 Write resize_video 调整视频尺寸

READ 2 tools

Read check_ffmpeg_status 检查FFmpeg是否已安装并可用 Read get_media_info 获取媒体文件信息

FAQ

Questions about FFmpeg MCP Tool

How do I prevent bulk modifications through FFmpeg MCP Tool? +

The FFmpeg MCP Tool server has 8 write tools including batch_compress_images, batch_compress_videos, compress_image. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach FFmpeg MCP Tool.

How many tools does the FFmpeg MCP Tool MCP server expose? +

10 tools across 2 categories: Read, Write. 2 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on FFmpeg MCP Tool? +

Register the FFmpeg MCP Tool MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every FFmpeg MCP Tool tool call.

Deterministic rules across all 10 FFmpeg MCP Tool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FFMPEG MCP TOOL →

Instant setup, no code required.

10 FFmpeg MCP Tool tools catalogued and risk-classified — across an index of 43,000+ MCP servers.