This record as markdown: /tools/coolify/get-service.md
What get_service does on Coolify
AI agents call get_service 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 get_service is rated Low
This tool retrieves service information by a unique identifier. It performs no modifications, deletions, or external operations. It is a straightforward data retrieval operation with minimal security risk unless the service data itself contains sensitive information, but the tool itself only reads without modifying state.
From the tool's definition Tool name 'get_service' combined with description 'Get a service by UUID' indicates a retrieval operation. The verb 'get' and the action of retrieving data by identifier are characteristic of read-only queries with no side effects.
Attacks that exploit this kind of access
The rule that runs get_service 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 get_service, this is the rule to start with:
get_service 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 get_service call is checked against it from then on.
Questions about get_service
Get a service by UUID. 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 get_service: 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.
get_service 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 get_service 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 get_service. 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.
get_service 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