Generate videos using AI models via Crazyrouter. Supports Sora 2, Kling V2, Veo 3, Seedance, Pika, and more.
AI agents invoke generate_video to trigger actions in Crazyrouter. 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 triggers an external AI video generation operation via a third-party API (Crazyrouter). It executes a compute-intensive external process that produces artifacts and likely incurs API usage costs, but does not directly move money or irreversibly destroy data. It falls under Execute as it triggers external operations whose effects depend on arguments.
From the tool's definition Generate videos using AI models via Crazyrouter. Supports Sora 2, Kling V2, Veo 3, Seedance, Pika, and more.
Attacks that exploit this kind of access
Generate videos using AI models via Crazyrouter. Supports Sora 2, Kling V2, Veo 3, Seedance, Pika, and more. It is categorised as a Execute tool in the Crazyrouter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crazyrouter MCP server in PolicyLayer and add a rule for generate_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 Crazyrouter. Nothing to install.
generate_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_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_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_video is provided by the Crazyrouter MCP server (xujfcn/crazyrouter-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 →