Find marker by custom data. Args: custom_data: Custom data to search for. item_index: 0-based item index. Default: 0.
AI agents call ti_get_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 read-only lookup operation on existing markers using custom data as a search criterion. It returns information about markers without creating, modifying, deleting, or executing any operations. The function signature (search parameters only, no mutation arguments) and the 'Find' verb confirm this is a non-destructive retrieval operation, placing it in the Read category with low severity.
From the tool's definition Tool name contains 'get' and description states 'Find marker by custom data' — indicates a search/query operation that retrieves existing marker information without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access ti_get_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 ti_get_marker_by_custom_data:
{
"version": "1",
"default": "deny",
"tools": {
"ti_get_marker_by_custom_data": {}
}
}ti_get_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.
Find marker by custom data. Args: custom_data: Custom data to search for. item_index: 0-based item index. Default: 0. 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_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.
ti_get_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 ti_get_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 ti_get_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.
ti_get_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.