inspect_custom_object

What inspect_custom_object does on DaVinci Resolve MCP

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

Why inspect_custom_object is rated Low

This tool retrieves or queries object metadata from the DaVinci Resolve API without creating, modifying, deleting, or executing any side effects. The verb 'inspect' signals read-only introspection. It belongs in the Read category with low severity because misuse would only expose internal object information, not cause destructive or operational harm.

From the tool's definition Tool name 'inspect_custom_object' and description 'Inspect a custom DaVinci Resolve API object by path' indicate inspection/querying of object properties with no modification or execution of external operations.

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

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

Questions about inspect_custom_object