Adds audio to a specific Luma AI generation based on a prompt.
AI agents use luma_add_audio 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.
This tool creates or modifies data (adding audio to a generation) without deleting or destroying information. While it alters an existing resource, the operation is reversible—the audio could be removed or replaced. It does not execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition The tool performs 'Adds audio to a specific Luma AI generation', which modifies an existing generation by attaching audio content to it. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access luma_add_audio 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_add_audio:
{
"version": "1",
"default": "deny",
"tools": {
"luma_add_audio": {
"limits": [
{
"counter": "luma_add_audio_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} luma_add_audio 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.
Adds audio to a specific Luma AI generation based on a prompt. 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_add_audio: 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_add_audio 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_add_audio 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_add_audio. 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_add_audio 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.