AI agents use resolve_add_marker_at to create or update resources in Resolve — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Resolve environment.
Adding markers to a timeline creates new metadata artifacts that modify the project state. This is reversible (markers can be deleted), so it falls under Write rather than Destructive. However, applied across a timeline, unauthorized marker addition could disrupt editing workflows, justifying medium severity. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'resolve_add_marker_at' indicates marker creation/modification in DaVinci Resolve. Sibling tools include 'resolve_add_markers', confirming this performs write operations on timeline metadata. Description is empty, limiting precision.
Attacks that exploit this kind of access
resolve_add_marker_at. It is categorised as a Write tool in the Resolve MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Resolve MCP server in PolicyLayer and add a rule for resolve_add_marker_at: 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 Resolve. Nothing to install.
resolve_add_marker_at 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 resolve_add_marker_at 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 resolve_add_marker_at. 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.
resolve_add_marker_at is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →