Inspect a custom DaVinci Resolve API object by path. Args: object_path: Path to the object using dot notation (e.g., 'resolve.GetMediaStorage()')
AI agents call inspect_custom_object 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.
This tool performs inspection and querying of DaVinci Resolve API objects. It accesses and returns information about object properties and state without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent can only read internal API state, which may expose metadata but cannot alter the project or trigger external actions.
From the tool's definition Tool name 'inspect_custom_object' and description 'Inspect a custom DaVinci Resolve API object by path' indicate querying/examining objects without modification.
Documented attack patterns abuse exactly the kind of access inspect_custom_object 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 inspect_custom_object:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_custom_object": {}
}
}inspect_custom_object is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inspect a custom DaVinci Resolve API object by path. Args: object_path: Path to the object using dot notation (e.g., 'resolve.GetMediaStorage()'). It is categorised as a Read tool in the DaVinci Resolve MCP MCP Server, which means it retrieves data without modifying state.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for inspect_custom_object: 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.
inspect_custom_object is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the inspect_custom_object 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 inspect_custom_object. 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.
inspect_custom_object 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.