refresh_lut_list
Refresh the LUT list in the project. Call after adding new LUT files.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/refresh-lut-list.md
What refresh_lut_list does on DaVinci Resolve MCP
AI agents invoke refresh_lut_list to trigger actions in DaVinci Resolve MCP. 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.
Why refresh_lut_list is rated High
This tool triggers an operational refresh/reload action within DaVinci Resolve — it causes the application to re-scan and update its internal LUT list. While it doesn't directly modify data, it executes an application-level operation with side effects (updating the project's LUT registry). It's not a pure read, and fits Execute as it triggers an external operation within the software.
From the tool's definition 'Refresh the LUT list in the project. Call after adding new LUT files.'
Attacks that exploit this kind of access
The rule that runs refresh_lut_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For refresh_lut_list, this is the rule to start with:
refresh_lut_list 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.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every refresh_lut_list call is checked against it from then on.
Questions about refresh_lut_list
Refresh the LUT list in the project. Call after adding new LUT files. It is categorised as a Execute tool in the DaVinci Resolve MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for refresh_lut_list: 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. Nothing to install.
refresh_lut_list 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 refresh_lut_list 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 refresh_lut_list. 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.
refresh_lut_list is provided by the DaVinci Resolve MCP server (samuelgursky/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DaVinci Resolve, and thousands of servers like it.
Across the catalogue