Update a Coolify server
AI agents use update_server to create or update resources in Coolify MCP Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify MCP Tools environment.
This tool modifies server configuration or properties (reversible in most cases) rather than executing arbitrary commands or deleting data. It falls under Write rather than Execute because the action itself is a configuration update, not execution of arbitrary code. However, the impact is significant because misconfigured server settings can cascade to many dependent services.
From the tool's definition Tool name 'update_server' and description 'Update a Coolify server' indicate modification of server configuration or state.
Attacks that exploit this kind of access
Update a Coolify server. It is categorised as a Write tool in the Coolify MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for update_server: 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 Tools. Nothing to install.
update_server 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_server 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_server. 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_server is provided by the Coolify MCP Tools MCP server (jplansink/coolify-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →