Edit a video using Runway Aleph. promptText is a prompt for the video. videoUri takes in a url of a video or a data uri of a video. Accepted Ratio values are 1280:720, 720:1280, 1104:832, 960:960, 832:1104, 1584:672, 848:480, 640:480. Use 1280:720 by default. It also accepts reference images, in ...
AI agents invoke runway_editVideo 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 AI video editing operation via the Runway API, whose effects depend on the input arguments (prompt, video URI, reference images, ratio). It is not a simple write/create of data but rather executes a generative/transformative process on an external platform. No irreversible deletion or financial transaction is involved, making Execute the most appropriate category.
From the tool's definition Edit a video using Runway Aleph. promptText is a prompt for the video. videoUri takes in a url of a video or a data uri of a video.
Documented attack patterns abuse exactly the kind of access runway_editVideo 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_editVideo:
{
"version": "1",
"default": "deny",
"tools": {
"runway_editVideo": {
"limits": [
{
"counter": "runway_editvideo_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runway_editVideo 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.
Edit a video using Runway Aleph. promptText is a prompt for the video. videoUri takes in a url of a video or a data uri of a video. Accepted Ratio values are 1280:720, 720:1280, 1104:832, 960:960, 832:1104, 1584:672, 848:480, 640:480. Use 1280:720 by default. It also accepts reference images, in the form of either a url or a base64 encoded image. Each reference image has a tag, which is a string that refers to the image from the user prompt. For example, if the user prompt is. 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_editVideo: 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_editVideo 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_editVideo 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_editVideo. 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_editVideo 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.