New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

validate_dctl_native

Validate shader source with Resolve 21.1. Source layout and native diagnostics are preserved; success means validation, not a rendered shader test.

SERVERDaVinci Resolve MCP SOURCEsamuelgursky/davinci-resolve-mcp
High RISK CLASS
Category Execute
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/validate-dctl-native.md

What validate_dctl_native does on DaVinci Resolve MCP

AI agents invoke validate_dctl_native to trigger actions in DaVinci Resolve MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why validate_dctl_native is rated High

Triggers Resolve's native shader validation engine, executing external diagnostic operations.

From the tool's definition Validate shader source with Resolve 21.1

Questions about validate_dctl_native

What does the validate_dctl_native tool do? +

Validate shader source with Resolve 21.1. Source layout and native diagnostics are preserved; success means validation, not a rendered shader test. It is categorised as a Execute tool in the DaVinci Resolve MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on validate_dctl_native? +

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

validate_dctl_native is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit validate_dctl_native? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of DaVinci Resolve's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.