generate_video · Hyper Video Service MCP: Risk & Policy

WHAT IT DOES

What generate_video does on Hyper Video Service

AI agents invoke generate_video to trigger actions in Hyper Video Service. 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 IT NEEDS A POLICY

Why generate_video needs a policy

This tool executes an external rendering pipeline: it creates an HTML+GSAP composition and runs headless Chrome to render it into an MP4. This constitutes execution of code and external operations whose effects depend on the input prompt.

From the tool's definition 'renders it to MP4 using headless Chrome' — triggers headless browser execution; 'Generate a video from a text prompt' — initiates an external rendering pipeline that runs code (HTML+GSAP composition) in a headless Chrome environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_video Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hyper Video Service, so you can run agents against it safely.

FAQ

Questions about generate_video

What does the generate_video tool do? +

Generate a video from a text prompt. The service creates a HyperFrames composition (HTML+GSAP), renders it to MP4 using headless Chrome, and returns a download URL when done. Styles:. It is categorised as a Execute tool in the Hyper Video Service MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_video? +

Register the Hyper Video Service 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 Hyper Video Service. Nothing to install.

What risk level is generate_video? +

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

Can I rate-limit generate_video? +

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.

How do I block generate_video completely? +

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.

What MCP server provides generate_video? +

generate_video is provided by the Hyper Video Service MCP server (twilson63/hyper-video-service). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.