Generate a video from an image and a text prompt. Accepted ratios are 1280:720, 720:1280, 1104:832, 832:1104, 960:960, 1584:672. Use 1280:720 by default. For duration, there are only either 5 or 10 seconds. Use 5 seconds by default. If the user asks to generate a video, always first use generateI...
AI agents invoke runway_generateVideo to trigger actions in Runway API 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.
This tool triggers an external video generation operation via the Runway API, consuming compute resources and producing media content. It is an Execute-category action because it initiates an external process whose effects depend on the provided arguments (image, prompt, ratio, duration). It is not purely Write since it runs a generative AI pipeline rather than storing user-supplied data.
From the tool's definition Generate a video from an image and a text prompt
Documented attack patterns abuse exactly the kind of access runway_generateVideo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Runway API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for runway_generateVideo:
{
"version": "1",
"default": "deny",
"tools": {
"runway_generateVideo": {
"limits": [
{
"counter": "runway_generatevideo_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runway_generateVideo 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.
Free to start. No card required.
Generate a video from an image and a text prompt. Accepted ratios are 1280:720, 720:1280, 1104:832, 832:1104, 960:960, 1584:672. Use 1280:720 by default. For duration, there are only either 5 or 10 seconds. Use 5 seconds by default. If the user asks to generate a video, always first use generateImage to generate an image first, then use the image to generate a video. It is categorised as a Execute tool in the Runway API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Runway API MCP Server MCP server in PolicyLayer and add a rule for runway_generateVideo: 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 Runway API MCP Server. Nothing to install.
runway_generateVideo 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 runway_generateVideo 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 runway_generateVideo. 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.
runway_generateVideo is provided by the Runway API MCP Server MCP server (runwayml/runway-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Runway API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Runway API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.