Transcribe audio for a clip. The transcription language follows the project's Speech Recognition setting (Project Settings > Subtitles), not a per-call argument. Args: clip_name: Name of the clip to transcribe use_speaker_detection: Optional (Resolve 21+). Enable speaker detection. If omitted, th...
AI agents invoke transcribe_audio 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.
Transcribing audio is not a simple read; it invokes a processing pipeline (speech recognition) that generates new data artifacts. It is not purely destructive or financial, but it executes an operation with real side effects on the project state, making Execute the most appropriate category.
From the tool's definition 'Transcribe audio for a clip' — triggers an external speech recognition/AI operation on a media clip, producing side effects (transcription data) that depend on arguments
Documented attack patterns abuse exactly the kind of access transcribe_audio gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for transcribe_audio:
{
"version": "1",
"default": "deny",
"tools": {
"transcribe_audio": {
"limits": [
{
"counter": "transcribe_audio_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}transcribe_audio 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.
Transcribe audio for a clip. The transcription language follows the project's Speech Recognition setting (Project Settings > Subtitles), not a per-call argument. Args: clip_name: Name of the clip to transcribe use_speaker_detection: Optional (Resolve 21+). Enable speaker detection. If omitted, the project's setting is used. 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 transcribe_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 DaVinci Resolve MCP. Nothing to install.
transcribe_audio 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 transcribe_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 transcribe_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.
transcribe_audio 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.
Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.