This record as markdown: /tools/coolify/update-application.md
What update_application does on Coolify
AI agents use update_application to create or update resources in Coolify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify environment.
Why update_application is rated Medium
The tool creates or modifies application data reversibly. While the exact scope of updates is not detailed, updating an application in a deployment/infrastructure platform like Coolify could affect running services, making it Write category with high severity due to potential blast radius (service disruption, configuration corruption).
From the tool's definition Tool name 'update_application' and description 'Update an application by UUID' indicates modification of existing application configuration or state.
Attacks that exploit this kind of access
The rule that runs update_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 update_application, this is the rule to start with:
update_application stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 update_application call is checked against it from then on.
Questions about update_application
Update an application by UUID. It is categorised as a Write tool in the Coolify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify MCP server in PolicyLayer and add a rule for update_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.
update_application is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue