Run IntelliSearch analysis on a clip (Resolve 21+, requires AI IntelliSearch Extra). Args: clip_id: Unique ID of the clip. identify_faces: Whether to identify faces. is_better_mode: Use Better mode (vs Faster).
AI agents invoke analyze_clip_for_intellisearch 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 pipeline on a clip rather than merely reading data. It triggers an external operation (IntelliSearch AI analysis) that processes the clip and likely writes analysis metadata back. Since it runs a computation with side effects, Execute is the appropriate category.
From the tool's definition 'Run IntelliSearch analysis on a clip' — triggers an AI analysis operation on a clip, which is an external computational process with side effects (modifying clip metadata/analysis results).
Documented attack patterns abuse exactly the kind of access analyze_clip_for_intellisearch 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_intellisearch:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_clip_for_intellisearch": {
"limits": [
{
"counter": "analyze_clip_for_intellisearch_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}analyze_clip_for_intellisearch 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 IntelliSearch analysis on a clip (Resolve 21+, requires AI IntelliSearch Extra). Args: clip_id: Unique ID of the clip. identify_faces: Whether to identify faces. is_better_mode: Use Better mode (vs Faster). 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_intellisearch: 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_intellisearch 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_intellisearch 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_intellisearch. 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_intellisearch 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.