put_file · FFmpeg MCP Server MCP: Risk & Policy

WHAT IT DOES

What put_file does on FFmpeg MCP Server

AI agents use put_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 put_file needs a policy

The 'put_file' tool, based on naming convention and server context around file management, most likely creates or modifies files in the sandbox. While the description is empty (reducing confidence), the tool name and presence of similar upload/write siblings strongly suggest this is a Write operation.

From the tool's definition Tool name 'put_file' indicates file write/upload operation; sibling tools include 'upload_file' and 'upload_file_to_gcs' which are Write operations; context describes file management capabilities in isolated sandbox.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

put_file Rate-limited

put_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": {
    "put_file": {
      "limits": [
        {
          "counter": "put_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 put_file

What does the put_file tool do? +

put_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 put_file? +

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

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

Can I rate-limit put_file? +

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

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

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