Upscales a specific Luma AI generation to a higher resolution.
AI agents use luma_upscale to create or update resources in RunwayML + Luma AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RunwayML + Luma AI MCP Server environment.
Upscaling creates a new higher-resolution version of an existing generation, which is a write/modify operation. It does not delete or overwrite the original irreversibly, and it doesn't execute code or move money. The blast radius is medium since it consumes API credits and modifies a generation asset.
From the tool's definition Upscales a specific Luma AI generation to a higher resolution
Documented attack patterns abuse exactly the kind of access luma_upscale gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RunwayML + Luma AI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for luma_upscale:
{
"version": "1",
"default": "deny",
"tools": {
"luma_upscale": {
"limits": [
{
"counter": "luma_upscale_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} luma_upscale stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upscales a specific Luma AI generation to a higher resolution. It is categorised as a Write tool in the RunwayML + Luma AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RunwayML + Luma AI MCP Server MCP server in PolicyLayer and add a rule for luma_upscale: 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 RunwayML + Luma AI MCP Server. Nothing to install.
luma_upscale is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the luma_upscale 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 luma_upscale. 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.
luma_upscale is provided by the RunwayML + Luma AI MCP Server MCP server (wheattoast11/mcp-video-gen). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RunwayML + Luma AI 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.
10 RunwayML + Luma AI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.