get_render_job_status
Get the status of a specific render job.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/get-render-job-status.md
What get_render_job_status does on DaVinci Resolve MCP
AI agents call get_render_job_status 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 get_render_job_status is rated Low
This tool only reads and returns status information about a render job. It has no side effects, does not modify data, does not execute operations, and does not delete or create resources. It is a pure information retrieval operation, fitting the Read category. The severity is low because querying job status poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_render_job_status' and description 'Get the status of a specific render job' indicate a query operation that retrieves information about an existing render job without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_render_job_status 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 get_render_job_status, this is the rule to start with:
get_render_job_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DaVinci Resolve MCP, apply this rule, and every get_render_job_status call is checked against it from then on.
Questions about get_render_job_status
Get the status of a specific render job. 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 get_render_job_status: 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.
get_render_job_status 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 get_render_job_status 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 get_render_job_status. 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.
get_render_job_status 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.
This server
Across the catalogue