Manage color groups and their node graphs. Actions: list() -> {groups} get_name(group_name) -> {name} set_name(group_name, new_name) -> {success} get_clips(group_name) -> {clips} get_pre_clip_graph(group_name) -> {available, num_nodes} get_post_clip_graph(group_name) -> {available, num_nodes}
AI agents use color_group 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.
The tool spans Read (list, get_name, get_clips, get_pre_clip_graph, get_post_clip_graph) and Write (set_name) operations. set_name creates a reversible modification to color group naming, which is a metadata change within the video editing project. This is reversible and does not execute arbitrary code or destroy data, so it classifies as Write.
From the tool's definition Tool includes set_name(group_name, new_name) which modifies color group metadata. Actions like get_name, list, get_clips, and get_*_graph are read-only, but the presence of set_name establishes the tool's primary capability as modification.
Documented attack patterns abuse exactly the kind of access color_group 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 color_group:
{
"version": "1",
"default": "deny",
"tools": {
"color_group": {
"limits": [
{
"counter": "color_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}color_group 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.
Free to start. No card required.
Manage color groups and their node graphs. Actions: list() -> {groups} get_name(group_name) -> {name} set_name(group_name, new_name) -> {success} get_clips(group_name) -> {clips} get_pre_clip_graph(group_name) -> {available, num_nodes} get_post_clip_graph(group_name) -> {available, num_nodes}. 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.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for color_group: 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.
color_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the color_group 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 color_group. 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.
color_group 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.