folder_perform_audio_classification
Classify audio of all clips in a Media Pool folder into categories (Resolve 21+).
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/folder-perform-audio-classification.md
What folder_perform_audio_classification does on DaVinci Resolve MCP
AI agents invoke folder_perform_audio_classification 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 folder_perform_audio_classification is rated High
This tool triggers an analysis/classification operation on all clips in a folder — it executes a processing action within DaVinci Resolve rather than simply reading data or writing metadata directly. The operation runs an automated audio classification workflow across potentially many clips, making it an Execute-category action.
From the tool's definition Classify audio of all clips in a Media Pool folder into categories
Attacks that exploit this kind of access
The rule that runs folder_perform_audio_classification 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 folder_perform_audio_classification, this is the rule to start with:
folder_perform_audio_classification 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 folder_perform_audio_classification call is checked against it from then on.
Questions about folder_perform_audio_classification
Classify audio of all clips in a Media Pool folder into categories (Resolve 21+). 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 folder_perform_audio_classification: 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.
folder_perform_audio_classification 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 folder_perform_audio_classification 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 folder_perform_audio_classification. 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.
folder_perform_audio_classification 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