upload_file · FFmpeg MCP Server MCP: Risk & Policy

WHAT IT DOES

What upload_file does on FFmpeg MCP Server

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

WHY IT NEEDS A POLICY

Why upload_file needs a policy

Upload operations create or modify data persistently. This is reversible (files can be deleted), so it falls under Write rather than Destructive. Severity is medium because unintended uploads could corrupt workflows or introduce malicious files, but the sandboxed FFmpeg environment and file management scope limit blast radius compared to arbitrary system writes.

From the tool's definition Tool name 'upload_file' indicates creation/modification of files. Sibling context shows integration with file management and Google Cloud Storage, suggesting persistent data modification. Description is empty, limiting certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_file Rate-limited

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

FAQ

Questions about upload_file

What does the upload_file tool do? +

upload_file. It is categorised as a Write tool in the FFmpeg 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 upload_file? +

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

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

Can I rate-limit upload_file? +

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

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

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