Run Slate analysis on a clip (Resolve 21+, requires AI Slate ID Extra). Args: clip_id: Unique ID of the clip. marker_color: Marker color for detected slates (Blue, Cyan, Green, Yellow, Red, Pink, Purple, Fuchsia, Rose, Lavender, Sky, Mint, Lemon, Sand, Cocoa, Cream).
AI agents invoke analyze_clip_for_slate 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.
This tool executes an AI analysis process on a clip and writes markers to the timeline as a result. It is not a pure read (it modifies the clip by adding markers) and not destructive. The most severe applicable category is Execute, as it triggers an external AI operation with side effects (marker creation). Severity is medium because misuse could add unwanted markers to clips but is reversible.
From the tool's definition 'Run Slate analysis on a clip' — triggers an AI analysis operation on a clip using an external AI engine (Resolve 21+, requires AI Slate ID Extra), and adds markers with a specified color as a side effect.
Documented attack patterns abuse exactly the kind of access analyze_clip_for_slate 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 analyze_clip_for_slate:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_clip_for_slate": {
"limits": [
{
"counter": "analyze_clip_for_slate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}analyze_clip_for_slate 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.
Run Slate analysis on a clip (Resolve 21+, requires AI Slate ID Extra). Args: clip_id: Unique ID of the clip. marker_color: Marker color for detected slates (Blue, Cyan, Green, Yellow, Red, Pink, Purple, Fuchsia, Rose, Lavender, Sky, Mint, Lemon, Sand, Cocoa, Cream). 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 analyze_clip_for_slate: 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.
analyze_clip_for_slate 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 analyze_clip_for_slate 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 analyze_clip_for_slate. 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.
analyze_clip_for_slate 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.