get_clip_flag_list

Get list of flags on a clip.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/get-clip-flag-list.md

WHAT IT DOES

What get_clip_flag_list does on DaVinci Resolve MCP

AI agents call get_clip_flag_list 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.

RISK

Why get_clip_flag_list is rated Low

This tool retrieves metadata (flags) associated with a video clip in DaVinci Resolve without modifying, deleting, or executing any operations. It is purely informational and has no destructive or financial impact. The blast radius of misuse is minimal—an AI agent obtaining flag information cannot cause harm to the project or system.

From the tool's definition Tool name 'get_clip_flag_list' with description 'Get list of flags on a clip' indicates a retrieval operation. The verb 'Get' and the function of listing existing flags confirms read-only access with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_clip_flag_list Allowed

get_clip_flag_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY 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 get_clip_flag_list call is checked against it from then on.

FAQ

Questions about get_clip_flag_list

What does the get_clip_flag_list tool do? +

Get list of flags on a clip. It is categorised as a Read tool in the DaVinci Resolve MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_clip_flag_list? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for get_clip_flag_list: 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 get_clip_flag_list? +

get_clip_flag_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_clip_flag_list? +

Yes. Add a rate_limit block to the get_clip_flag_list 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 get_clip_flag_list completely? +

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

get_clip_flag_list 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →