Low Risk

get_resolve_version_fields

Get DaVinci Resolve version as structured fields [major, minor, patch, build, suffix].

How to control get_resolve_version_fields ↓

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

Low Risk

This tool queries and returns version metadata about the DaVinci Resolve application. It performs a read-only operation with no side effects, no code execution, and no data modification. The severity is low because version information is non-sensitive operational metadata; misuse poses minimal risk to the system or workflow.

From the tool's definition Tool name 'get_resolve_version_fields' and description 'Get DaVinci Resolve version as structured fields' indicate retrieval of version information with no modification or execution.

Documented attack patterns abuse exactly the kind of access get_resolve_version_fields 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 get_resolve_version_fields:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_resolve_version_fields": {}
  }
}

get_resolve_version_fields is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register DaVinci Resolve MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_resolve_version_fields tool do? +

Get DaVinci Resolve version as structured fields [major, minor, patch, build, suffix]. 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_resolve_version_fields? +

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

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

Can I rate-limit get_resolve_version_fields? +

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

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

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

Enforce policy on every DaVinci Resolve MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.