stop_rendering
Stop the current rendering process.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/stop-rendering.md
What stop_rendering does on DaVinci Resolve MCP
AI agents invoke stop_rendering 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 stop_rendering is rated High
This tool executes a command that interrupts an ongoing operation in the video editing software. While not destructive (the rendered output or project data is not deleted), it forcibly terminates an active process, which qualifies as Execute.
From the tool's definition The tool 'stop_rendering' stops a rendering process that is currently in progress. This represents an action that triggers an external operation (halting an active render job in DaVinci Resolve) whose effects depend on the state of the system.
Attacks that exploit this kind of access
The rule that runs stop_rendering 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 stop_rendering, this is the rule to start with:
stop_rendering stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 stop_rendering call is checked against it from then on.
Questions about stop_rendering
Stop the current rendering process. 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.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for stop_rendering: 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.
stop_rendering is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_rendering 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 stop_rendering. 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.
stop_rendering 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.
Across the catalogue