Critical Risk →

quit_app

Quit DaVinci Resolve application. Args: force: Whether to force quit even if unsaved changes (potentially dangerous) save_project: Whether to save the project before quitting

How to control quit_app ↓

AI agents call quit_app to permanently remove resources in DaVinci Resolve MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool terminates the entire application, which is irreversible in the moment and can cause loss of unsaved work. The 'force' flag explicitly warns it is 'potentially dangerous' as it bypasses unsaved change protection. Even with save_project=true, forcibly closing a professional video editing application mid-session can corrupt project state or lose work, making this Destructive in nature.

From the tool's definition 'Quit DaVinci Resolve application' with parameter 'force: Whether to force quit even if unsaved changes (potentially dangerous)'

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "quit_app"
  ]
}

quit_app disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the quit_app tool do? +

Quit DaVinci Resolve application. Args: force: Whether to force quit even if unsaved changes (potentially dangerous) save_project: Whether to save the project before quitting. It is categorised as a Destructive tool in the DaVinci Resolve MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on quit_app? +

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

quit_app is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit quit_app? +

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

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

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