Get a marker by its custom data string. Args: clip_id: Unique ID of the clip. custom_data: Custom data string to search for.
AI agents call get_clip_marker_by_custom_data to retrieve information from DaVinci Resolve MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/lookup operation within DaVinci Resolve to retrieve marker information based on custom data attributes. It has no side effects—it does not modify the timeline, markers, clips, or any other project state. The operation is purely informational and reversible by nature (retrieving data that already exists). This fits the 'Read' category as it retrieves data without side effects.
From the tool's definition Tool name 'get_clip_marker_by_custom_data' and description 'Get a marker' indicate retrieval/query functionality.
Documented attack patterns abuse exactly the kind of access get_clip_marker_by_custom_data 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 get_clip_marker_by_custom_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_clip_marker_by_custom_data": {}
}
}get_clip_marker_by_custom_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a marker by its custom data string. Args: clip_id: Unique ID of the clip. custom_data: Custom data string to search for. It is categorised as a Read tool in the DaVinci Resolve MCP MCP Server, which means it retrieves data without modifying state.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for get_clip_marker_by_custom_data: 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.
get_clip_marker_by_custom_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_clip_marker_by_custom_data 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 get_clip_marker_by_custom_data. 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.
get_clip_marker_by_custom_data 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.