ti_get_marker_custom_data
Get marker custom data.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/ti-get-marker-custom-data.md
What ti_get_marker_custom_data does on DaVinci Resolve MCP
AI agents call ti_get_marker_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_custom_data is rated Low
This tool retrieves metadata associated with markers in a video editing timeline. Getting/reading data is a Read operation with minimal security risk—it does not modify, delete, or execute actions. The blast radius of misuse is low since the AI agent can only access existing marker information without the ability to change project state or trigger external operations.
From the tool's definition Tool name 'ti_get_marker_custom_data' and description 'Get marker custom data' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs ti_get_marker_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_custom_data, this is the rule to start with:
ti_get_marker_custom_data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every ti_get_marker_custom_data call is checked against it from then on.
Questions about ti_get_marker_custom_data
Get marker custom data. 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 ti_get_marker_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.
ti_get_marker_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 ti_get_marker_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 ti_get_marker_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.
ti_get_marker_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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue