update_clip_marker_custom_data

Update the custom data of a clip marker.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/update-clip-marker-custom-data.md

WHAT IT DOES

What update_clip_marker_custom_data does on DaVinci Resolve MCP

AI agents use update_clip_marker_custom_data to create or update resources in DaVinci Resolve MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment.

RISK

Why update_clip_marker_custom_data is rated Medium

This tool modifies metadata associated with clip markers in a video project. While the change is reversible (can be undone/re-updated), it affects project state. The impact is localized to marker metadata rather than core media or timeline structure, making it Write rather than Execute.

From the tool's definition Tool name 'update_clip_marker_custom_data' uses the verb 'update', which modifies existing data (the custom data associated with a clip marker). The description confirms it 'Update[s] the custom data', indicating a reversible modification operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_clip_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 update_clip_marker_custom_data, this is the rule to start with:

update_clip_marker_custom_data Rate-limited

update_clip_marker_custom_data stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_clip_marker_custom_data": {
      "limits": [
        {
          "counter": "update_clip_marker_custom_data_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every update_clip_marker_custom_data call is checked against it from then on.

FAQ

Questions about update_clip_marker_custom_data

What does the update_clip_marker_custom_data tool do? +

Update the custom data of a clip marker. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_clip_marker_custom_data? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for update_clip_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.

What risk level is update_clip_marker_custom_data? +

update_clip_marker_custom_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_clip_marker_custom_data? +

Yes. Add a rate_limit block to the update_clip_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.

How do I block update_clip_marker_custom_data completely? +

Set action: deny in the PolicyLayer policy for update_clip_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.

What MCP server provides update_clip_marker_custom_data? +

update_clip_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.

KEEP EXPLORING

More on DaVinci Resolve, and thousands of servers like it.

This server

All 355 DaVinci Resolve tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →