Low Risk

find_video_path

可以查找视频文件路径,查找文件路径,递归查找精确匹配文件名的视频文件路径(支持带或不带扩展名) 参数: root_path - 要搜索的根目录 video_name - 视频文件名(可以带扩展名,但会忽略扩展名匹配) 返回: 首个匹配的视频文件完整路径,找不到时返回空字符串

How to control find_video_path ↓

AI agents call find_video_path to retrieve information from FFmpeg-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

find_video_path performs file system search and retrieval only. It takes a root directory and video filename as input, then returns matching file paths. There are no side effects, data modifications, code execution, or file system changes. This is a straightforward read operation similar to a filesystem search utility.

From the tool's definition Tool description states it 'can find video file paths' and 'recursively find video file paths matching exact filename'. The function returns 'the complete path of the first matching video file' with no modification, deletion, or execution capabilities.

Documented attack patterns abuse exactly the kind of access find_video_path gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and FFmpeg-MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_video_path:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_video_path": {}
  }
}

find_video_path is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register FFmpeg-MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the find_video_path tool do? +

可以查找视频文件路径,查找文件路径,递归查找精确匹配文件名的视频文件路径(支持带或不带扩展名) 参数: root_path - 要搜索的根目录 video_name - 视频文件名(可以带扩展名,但会忽略扩展名匹配) 返回: 首个匹配的视频文件完整路径,找不到时返回空字符串. It is categorised as a Read tool in the FFmpeg-MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_video_path? +

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

find_video_path is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_video_path? +

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

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

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

Enforce policy on every FFmpeg-MCP Server tool call.

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

Free to start. No card required.

8 FFmpeg-MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.