Apply a grade from a .drx file to a timeline item's graph. Args: drx_path: Absolute path to the .drx file. grade_mode: 0=No keyframes, 1=Source Timecode aligned, 2=Start Frames aligned. item_index: 0-based timeline item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_in...
AI agents use graph_apply_grade_from_drx 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.
This tool modifies project state by applying grades and potentially adding keyframes to video tracks. It is Write-category because the changes are reversible (grades can be adjusted, keyframes can be removed, and the original timeline state can be restored). It is not Destructive since no data is irreversibly deleted or overwritten.
From the tool's definition Tool applies a grade from a .drx file to a timeline item's graph, modifying color grading and keyframe data. The action creates or modifies color correction metadata in the project (keyframes, grade parameters) in a reversible manner.
Documented attack patterns abuse exactly the kind of access graph_apply_grade_from_drx 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 graph_apply_grade_from_drx:
{
"version": "1",
"default": "deny",
"tools": {
"graph_apply_grade_from_drx": {
"limits": [
{
"counter": "graph_apply_grade_from_drx_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}graph_apply_grade_from_drx 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.
Apply a grade from a .drx file to a timeline item's graph. Args: drx_path: Absolute path to the .drx file. grade_mode: 0=No keyframes, 1=Source Timecode aligned, 2=Start Frames aligned. item_index: 0-based timeline item index. Default: 0. track_type: 'video' or 'audio'. Default: 'video'. track_index: 1-based track index. Default: 1. 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 graph_apply_grade_from_drx: 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.
graph_apply_grade_from_drx 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 graph_apply_grade_from_drx 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 graph_apply_grade_from_drx. 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.
graph_apply_grade_from_drx 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.