Execute a Lua script in Resolve's Fusion environment.
AI agents invoke execute_lua to trigger actions in DaVinci Resolve 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 allows execution of arbitrary Lua scripts within DaVinci Resolve's Fusion environment. Lua script execution is a form of code execution that can trigger complex operations with side effects dependent on script content.
From the tool's definition Tool name 'execute_lua' and description 'Execute a Lua script in Resolve's Fusion environment' explicitly indicate arbitrary code execution capability.
Documented attack patterns abuse exactly the kind of access execute_lua gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_lua:
{
"version": "1",
"default": "deny",
"tools": {
"execute_lua": {
"limits": [
{
"counter": "execute_lua_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_lua 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.
Execute a Lua script in Resolve's Fusion environment. It is categorised as a Execute tool in the DaVinci Resolve MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP Server MCP server in PolicyLayer and add a rule for execute_lua: 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 DaVinci Resolve MCP Server. Nothing to install.
execute_lua 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 execute_lua 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 execute_lua. 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.
execute_lua is provided by the DaVinci Resolve MCP Server MCP server (tooflex/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DaVinci Resolve 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.
32 DaVinci Resolve MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.