Start a specific application using its UUID. This initiates the application and makes it available for use.
AI agents invoke start-application to trigger actions in Coolify MCP Server. 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 an operation that starts an application instance, which is an irreversible action that initiates external processes and changes system state. While not destructive (the application can be stopped), it is an Execute-category action because it triggers an external operation whose side effects are not immediately reversible at the tool level and depend on the argument (application UUID).
From the tool's definition Tool description states it 'Start a specific application' which triggers an external operation (application startup) whose effects depend on which application UUID is provided.
Documented attack patterns abuse exactly the kind of access start-application gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coolify MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start-application:
{
"version": "1",
"default": "deny",
"tools": {
"start-application": {
"limits": [
{
"counter": "start-application_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} start-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.
Free to start. No card required.
Start a specific application using its UUID. This initiates the application and makes it available for use. It is categorised as a Execute tool in the Coolify MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for start-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 MCP Server. Nothing to install.
start-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 start-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 start-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.
start-application is provided by the Coolify MCP Server MCP server (stumason/coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coolify MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Coolify MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.