Restart DaVinci Resolve application. Args: wait_seconds: Seconds to wait between quit and restart
AI agents invoke restart_app 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.
This tool executes a command that terminates and restarts a running application process. While not destructive to data (reversible by restarting again), it is an Execute category tool because it triggers external system operations whose effects depend on timing arguments and cannot be undone instantaneously.
From the tool's definition Tool name 'restart_app' with description 'Restart DaVinci Resolve application' indicates execution of an application lifecycle operation (quit and restart).
Documented attack patterns abuse exactly the kind of access restart_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 restart_app:
{
"version": "1",
"default": "deny",
"tools": {
"restart_app": {
"limits": [
{
"counter": "restart_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restart_app 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.
Free to start. No card required.
Restart DaVinci Resolve application. Args: wait_seconds: Seconds to wait between quit and restart. 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 restart_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.
restart_app 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 restart_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.
Set action: deny in the PolicyLayer policy for restart_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.
restart_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.
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.