This record as markdown: /tools/coolify/restart-application.md
What restart_application does on Coolify
AI agents invoke restart_application to trigger actions in Coolify. 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 restart_application is rated High
This tool executes an action that triggers a restart of an application, similar to running a shell command or triggering an external operation. While not permanently destructive, a restart can interrupt service availability, cause data loss if the application has unflushed state, and impact end users. It is not reversible in the sense that the downtime and any in-flight requests are lost.
From the tool's definition Tool named 'restart_application' with description 'Restart an application.' The verb 'restart' triggers an external operation (restarting a running service/application) whose effects depend on which application is specified as an argument.
Attacks that exploit this kind of access
The rule that runs restart_application safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restart_application, this is the rule to start with:
restart_application 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 Coolify, apply this rule, and every restart_application call is checked against it from then on.
Questions about restart_application
Restart an application. It is categorised as a Execute tool in the Coolify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coolify MCP server in PolicyLayer and add a rule for restart_application: 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 Coolify. Nothing to install.
restart_application 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_application 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_application. 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_application is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coolify, and thousands of servers like it.
Across the catalogue