创建带字幕的视频
AI agents invoke create_video_with_subtitles_tool to trigger actions in Auto Video Generator. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a complex media processing pipeline (subtitle embedding, voice synthesis, video editing via FFmpeg) that produces new files on the system. It spans Write and Execute; Execute is more appropriate because it runs external processes (FFmpeg, TTS engine) whose effects depend on arguments.
From the tool's definition '创建带字幕的视频' (Create video with subtitles) — triggers an external video generation/editing operation that synthesizes voice, processes clips, and writes output files
Attacks that exploit this kind of access
创建带字幕的视频. It is categorised as a Execute tool in the Auto Video Generator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Auto Video Generator MCP server in PolicyLayer and add a rule for create_video_with_subtitles_tool: 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.
create_video_with_subtitles_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_video_with_subtitles_tool 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 create_video_with_subtitles_tool. 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.
create_video_with_subtitles_tool 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 →