resize_video · FFmpeg MCP Server MCP: Risk & Policy

WHAT IT DOES

What resize_video does on FFmpeg MCP Server

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

This tool executes an FFmpeg operation to process and transform video content. It is not a simple read (it produces new output), not a write to a persistent store in the traditional sense, and not destructive (original data is not deleted). It runs an external media processing operation whose effects depend on the input arguments, fitting the Execute category.

From the tool's definition 'Resize a video to one or more standard resolutions' — triggers FFmpeg processing pipeline to transform video data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resize_video Rate-limited

resize_video 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": {
    "resize_video": {
      "limits": [
        {
          "counter": "resize_video_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 resize_video

What does the resize_video tool do? +

Resize a video to one or more standard resolutions (360p, 480p, 720p, 1080p). 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 resize_video? +

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

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

Can I rate-limit resize_video? +

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

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

resize_video is provided by the FFmpeg MCP Server MCP server (windsornguyen/ffmpeg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.