Modify an existing keyframe by changing its value or frame position. Args: timeline_item_id: The ID of the timeline item property_name: The name of the property with keyframe frame: Current frame position of the keyframe to modify new_value: Optional new value for the keyframe new_frame: Optional...
AI agents use modify_keyframe 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 creates or modifies animation keyframe data reversibly (can be undone/changed again), fitting the Write category. It affects video timeline state but does not delete content (ruling out Destructive) or execute arbitrary code (ruling out Execute). Severity is medium because misuse could corrupt a video project's animation layers, but the effect is confined to keyframe metadata and remains reversible.
From the tool's definition modify_keyframe changes existing keyframe values or frame positions in video editing timeline—'Modify an existing keyframe by changing its value or frame position'—which reversibly alters animation/effect data without deletion.
Documented attack patterns abuse exactly the kind of access modify_keyframe 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 modify_keyframe:
{
"version": "1",
"default": "deny",
"tools": {
"modify_keyframe": {
"limits": [
{
"counter": "modify_keyframe_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_keyframe 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.
Modify an existing keyframe by changing its value or frame position. Args: timeline_item_id: The ID of the timeline item property_name: The name of the property with keyframe frame: Current frame position of the keyframe to modify new_value: Optional new value for the keyframe new_frame: Optional new frame position for the keyframe. 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 modify_keyframe: 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.
modify_keyframe 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 modify_keyframe 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 modify_keyframe. 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.
modify_keyframe 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.