合并多个视频
AI agents use merge_videos_tool to create or update resources in Auto Video Generator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Auto Video Generator environment.
Merging videos creates new composite media files by combining and modifying existing video data. This is a Write operation because it produces new or modified data artifacts reversibly—the original videos remain intact and the merge can be undone by deleting the output. It does not execute arbitrary code (Execute), permanently destroy data (Destructive), or involve financial transactions (Financial).
From the tool's definition Tool name 'merge_videos_tool' and description '合并多个视频' (merge multiple videos) indicate creation/modification of video files through combining existing clips.
Attacks that exploit this kind of access
合并多个视频. It is categorised as a Write tool in the Auto Video Generator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Auto Video Generator MCP server in PolicyLayer and add a rule for merge_videos_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.
merge_videos_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_videos_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 merge_videos_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.
merge_videos_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 →