generate_video
Generate a video from a text prompt (or an image/video reference) using AI. CoWork OS will pick the best configured provider automatically (OpenAI Sora 2 / Azure Sora 2 / Gemini Veo 3.1 / Vertex AI Veo / Kling), unless you specify a provider. Modes: - text_to_video (default): generate a video fro...
This record as markdown: /tools/cowork-os/generate-video.md
What generate_video does on CoWork OS
AI agents invoke generate_video to trigger actions in CoWork OS. 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.
Why generate_video is rated High
This tool triggers an external AI service call to generate video content, which constitutes executing an operation with external side effects (API calls, compute costs, file creation). It is not purely a read operation, and the output depends on the arguments provided.
From the tool's definition Generate a video from a text prompt (or an image/video reference) using AI... CoWork OS will pick the best configured provider automatically (OpenAI Sora 2 / Azure Sora 2 / Gemini Veo 3.1 / Vertex AI Veo / Kling)
Attacks that exploit this kind of access
The rule that runs generate_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_video, this is the rule to start with:
generate_video stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every generate_video call is checked against it from then on.
Questions about generate_video
Generate a video from a text prompt (or an image/video reference) using AI. CoWork OS will pick the best configured provider automatically (OpenAI Sora 2 / Azure Sora 2 / Gemini Veo 3.1 / Vertex AI Veo / Kling), unless you specify a provider. Modes: - text_to_video (default): generate a video from a text prompt - image_to_video: animate a reference image (referenceImagePath required) - video_to_video: restyle or reprompt an existing video (provider-native, referenceVideoPath required) - extend_video: extend the duration of an existing video (provider-native, referenceVideoPath required) Provider support: - openai: Sora 2 — text_to_video, image_to_video - azure: Sora 2 via Azure OpenAI deployment (. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CoWork OS 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 CoWork OS. 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 CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue