检查FFmpeg状态
AI agents call check_ffmpeg_status to retrieve information from Auto Video Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the operational state of FFmpeg, a video processing library. Status checks are read-only operations that retrieve information about system components without modifying, deleting, or executing arbitrary operations. The tool falls squarely into the Read category with low severity risk, as misuse by an AI agent would only expose system state information rather than cause harmful side effects.
From the tool's definition Tool name 'check_ffmpeg_status' and description '检查FFmpeg状态' (Check FFmpeg status) indicate a status-checking operation with no side effects.
Attacks that exploit this kind of access
检查FFmpeg状态. It is categorised as a Read tool in the Auto Video Generator MCP Server, which means it retrieves data without modifying state.
Register the Auto Video Generator MCP server in PolicyLayer and add a rule for check_ffmpeg_status: 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 Auto Video Generator. Nothing to install.
check_ffmpeg_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_ffmpeg_status 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.
Set action: deny in the PolicyLayer policy for check_ffmpeg_status. 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.
check_ffmpeg_status is provided by the Auto Video Generator MCP server (zgmurder/auto_video_generator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →