AI agents use generate_img_to_video to create or update resources in Vidu MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vidu MCP environment.
Based on the tool name and server context, this tool generates (creates) a new video from an image input. This is a Write operation as it creates new content. The description is empty so confidence is reduced. Severity is medium as misuse could incur API costs or generate unwanted content, but no data is destroyed or financial transactions are made directly.
From the tool's definition Tool name 'generate_img_to_video' and server description 'generates high-quality videos from text, images, and reference content' — the tool likely creates video content from an image input.
Attacks that exploit this kind of access
generate_img_to_video. It is categorised as a Write tool in the Vidu MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vidu MCP server in PolicyLayer and add a rule for generate_img_to_video: 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 Vidu MCP. Nothing to install.
generate_img_to_video 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 generate_img_to_video 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 generate_img_to_video. 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.
generate_img_to_video is provided by the Vidu MCP server (shengshu-ai/vidu-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 →