This record as markdown: /tools/coolify/list-servers.md
What list_servers does on Coolify
AI agents call list_servers to retrieve information from Coolify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_servers is rated Low
This tool retrieves and displays information about servers without creating, modifying, deleting, or executing any operations. It is a standard query operation with no side effects, fitting the Read category. Severity is low because listing servers provides inventory information but does not directly expose sensitive capabilities or enable destructive actions without further tool usage.
From the tool's definition Tool name is 'list_servers' and description states 'List all servers registered in Coolify.' The verb 'list' and action of retrieving/querying server information with no modification indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs list_servers 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 list_servers, this is the rule to start with:
list_servers is read-only, so it stays allowed. 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 list_servers call is checked against it from then on.
Questions about list_servers
List all servers registered in Coolify. It is categorised as a Read tool in the Coolify MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP server in PolicyLayer and add a rule for list_servers: 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.
list_servers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_servers 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 list_servers. 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.
list_servers 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