Render motion-deblurred copies of all clips in a folder (Resolve 21+). Creates NEW media files; source media is not modified. Args: folder_path: Path from root. Empty for current folder. deblur_option: Settings dict (FileName, Format, Codec, EncodingProfile, UseExtremeMode, UseMarkInMarkOut, Rend...
AI agents use folder_remove_motion_blur to create or update resources in DaVinci Resolve MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment.
The tool renders new media files (motion-deblurred copies) to disk. Source media is explicitly stated to be unmodified, so this is not Destructive. It creates new files on the filesystem, making it a Write operation. Severity is medium as it can create many files across an entire folder of clips, potentially consuming significant disk space.
From the tool's definition Creates NEW media files; source media is not modified.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access folder_remove_motion_blur 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 folder_remove_motion_blur:
{
"version": "1",
"default": "deny",
"tools": {
"folder_remove_motion_blur": {
"limits": [
{
"counter": "folder_remove_motion_blur_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}folder_remove_motion_blur stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Render motion-deblurred copies of all clips in a folder (Resolve 21+). Creates NEW media files; source media is not modified. Args: folder_path: Path from root. Empty for current folder. deblur_option: Settings dict (FileName, Format, Codec, EncodingProfile, UseExtremeMode, UseMarkInMarkOut, RenderAtSourceRes, UseMoreGpuMemory). It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for folder_remove_motion_blur: 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_remove_motion_blur is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the folder_remove_motion_blur 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_remove_motion_blur. 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_remove_motion_blur 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.