AI agents use timeline_versioning 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.
Timeline versioning typically involves creating snapshots or versions of editing timelines, which are reversible modifications to project state. Without explicit description, this appears to be a Write operation (creating/storing versions) rather than Read (querying versions) or Destructive (deleting them).
From the tool's definition Tool named 'timeline_versioning' on a video editing MCP server; no description provided, but naming and context suggest creation or modification of timeline versions/checkpoints.
Documented attack patterns abuse exactly the kind of access timeline_versioning 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 timeline_versioning:
{
"version": "1",
"default": "deny",
"tools": {
"timeline_versioning": {
"limits": [
{
"counter": "timeline_versioning_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}timeline_versioning 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.
timeline_versioning. 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 timeline_versioning: 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.
timeline_versioning 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 timeline_versioning 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 timeline_versioning. 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.
timeline_versioning 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.