generate_text_to_video
AI agents invoke generate_text_to_video to trigger actions in Wan2GP MCP Server. 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.
The tool triggers an external video generation operation on a Gradio server, which is an Execute-category action. The description is empty, so classification relies on the tool name and server context. Sibling tools like 'generate_image_to_video' and 'get_generation_status' confirm this server orchestrates media generation jobs.
From the tool's definition Tool name 'generate_text_to_video' on a server that 'Enables AI assistants to generate videos from text prompts and images by interfacing with a Wan2GP Gradio server'
Attacks that exploit this kind of access
generate_text_to_video. It is categorised as a Execute tool in the Wan2GP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wan2GP MCP Server MCP server in PolicyLayer and add a rule for generate_text_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 Wan2GP MCP Server. Nothing to install.
generate_text_to_video 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 generate_text_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_text_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_text_to_video is provided by the Wan2GP MCP Server MCP server (reverb256/wan2gp-mcp-server). 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 →