generate_video_veo

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

High RISK CLASS

Category Execute

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/generate-video-veo.md

WHAT IT DOES

What generate_video_veo does on Freedom Mcp

AI agents invoke generate_video_veo to trigger actions in Freedom Mcp. 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.

Parameter	Type	Required	Description
`prompt`	string	Yes	Detailed cinematic description of the video. Include visual scene, camera direction, lighting, audio, and brand elements.
`quality`	string	—	Quality mode. "fast" for quick previews, "cinematic" (default) for premium quality.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`aspect_ratio`	string	—	Aspect ratio. 16:9 for landscape, 9:16 for vertical/Reels, 1:1 for square.
`save_to_drive`	boolean	—	If true, also save the video to Google Drive. Defaults to false.
`reference_image_url`	string	—	Optional URL of an image to animate (image-to-video). Use the image_url from a previous generate_image result.

Parameters from the server's own tool schema.

RISK

Why generate_video_veo is rated High

Triggers external AI video generation consuming credits via a multi-step agent process.

From the tool's definition Generate a high-fidelity cinematic video using Google Veo 3.1 (5 credits)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs generate_video_veo safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_video_veo, this is the rule to start with:

generate_video_veo Rate-limited

generate_video_veo 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_video_veo": {
      "limits": [
        {
          "counter": "generate_video_veo_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every generate_video_veo call is checked against it from then on.

FAQ

Questions about generate_video_veo

What does the generate_video_veo tool do? +

Generate a high-fidelity cinematic video using Google Veo 3.1 (5 credits). Premium quality with realistic physics and cinematic lighting. Use ONLY for final deliverables — landing page videos, polished ad creatives, brand content. NEVER use for first drafts. Always iterate with generate_video first, then upgrade to Veo for the final version. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does generate_video_veo accept? +

generate_video_veo accepts 6 parameters: prompt, quality, companyId, aspect_ratio, save_to_drive, reference_image_url. Required: prompt, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_video_veo? +

Register the Freedom MCP server in PolicyLayer and add a rule for generate_video_veo: 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 Freedom Mcp. Nothing to install.

What risk level is generate_video_veo? +

generate_video_veo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit generate_video_veo? +

Yes. Add a rate_limit block to the generate_video_veo 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.

How do I block generate_video_veo completely? +

Set action: deny in the PolicyLayer policy for generate_video_veo. 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.

What MCP server provides generate_video_veo? +

generate_video_veo is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools → High-risk tools on this server →

Across the catalogue

ai_generate on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →