ti_get_marker_by_custom_data

What ti_get_marker_by_custom_data does on DaVinci Resolve MCP

AI agents call ti_get_marker_by_custom_data to retrieve information from DaVinci Resolve MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ti_get_marker_by_custom_data is rated Low

This tool retrieves existing marker metadata without modifying, deleting, or executing external operations. It is a pure read operation with no side effects. The severity is low as misuse would only expose marker metadata within an existing DaVinci Resolve project, with no capability to modify timelines, delete content, or trigger external processes.

From the tool's definition Tool name 'ti_get_marker_by_custom_data' and description 'Find marker by custom data' indicate a query/retrieval operation that searches for and returns marker information based on custom data criteria.

The rule that runs ti_get_marker_by_custom_data safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ti_get_marker_by_custom_data, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ti_get_marker_by_custom_data": {}
  }
}

Questions about ti_get_marker_by_custom_data