Low Risk

get_video_info

获取视频信息,包括时长,帧率,codec等 参数: video_path (str): 输入视频文件路径 返回: 视频详细信息

How to control get_video_info ↓

AI agents call get_video_info 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

This is a straightforward metadata query operation. It reads properties from an existing video file without side effects, making it a Read category tool. Severity is low because misuse cannot cause harm—at worst, an agent could read information about videos, which poses minimal risk. Confidence is high given the explicit statement that it retrieves video properties.

From the tool's definition Tool retrieves video metadata ('获取视频信息,包括时长,帧率,codec等' = 'Get video information, including duration, frame rate, codec, etc.'). The parameter is a read-only input (video_path) and the return value is informational (视频详细信息 = 'video detailed information').

Documented attack patterns abuse exactly the kind of access get_video_info 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 get_video_info:

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

get_video_info 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 get_video_info tool do? +

获取视频信息,包括时长,帧率,codec等 参数: video_path (str): 输入视频文件路径 返回: 视频详细信息. 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 get_video_info? +

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

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

Can I rate-limit get_video_info? +

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

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

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