Critical Risk →

luma_delete_generation

Deletes a specific Luma AI generation.

How to control luma_delete_generation ↓

What luma_delete_generation does on RunwayML + Luma AI MCP Server

AI agents call luma_delete_generation to permanently remove resources in RunwayML + Luma AI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why luma_delete_generation needs a policy

The tool performs an irreversible deletion of user-created data (a Luma AI generation). Once deleted, the generation cannot be recovered. This is a classic Destructive action that cannot be undone, fitting the definition exactly.

From the tool's definition Tool name contains 'delete' and description states 'Deletes a specific Luma AI generation' — this irreversibly removes generated content.

Documented attack patterns abuse exactly the kind of access luma_delete_generation gives an agent:

How to control luma_delete_generation

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_delete_generation:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "luma_delete_generation"
  ]
}

luma_delete_generation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register RunwayML + Luma AI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about luma_delete_generation

What does the luma_delete_generation tool do? +

Deletes a specific Luma AI generation. It is categorised as a Destructive tool in the RunwayML + Luma AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on luma_delete_generation? +

Register the RunwayML + Luma AI MCP Server MCP server in PolicyLayer and add a rule for luma_delete_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.

What risk level is luma_delete_generation? +

luma_delete_generation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit luma_delete_generation? +

Yes. Add a rate_limit block to the luma_delete_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.

How do I block luma_delete_generation completely? +

Set action: deny in the PolicyLayer policy for luma_delete_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.

What MCP server provides luma_delete_generation? +

luma_delete_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.

Enforce policy on every RunwayML + Luma AI MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.