Gets details for a specific Luma AI generation.
AI agents call luma_get_generation to retrieve information from RunwayML + Luma AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata or status information about a previously created generation. It performs a query/fetch operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker gains only read access to generation details they may already have identifiers for.
From the tool's definition Tool name 'luma_get_generation' and description 'Gets details for a specific Luma AI generation' indicate retrieval of existing data without modification or side effects.
Documented attack patterns abuse exactly the kind of access luma_get_generation 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_get_generation:
{
"version": "1",
"default": "deny",
"tools": {
"luma_get_generation": {}
}
} luma_get_generation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets details for a specific Luma AI generation. It is categorised as a Read tool in the RunwayML + Luma AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunwayML + Luma AI MCP Server MCP server in PolicyLayer and add a rule for luma_get_generation: 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_get_generation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the luma_get_generation 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_get_generation. 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_get_generation 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.