get_service_logs

Get logs from a service. NOTE: This endpoint is not available in Coolify API and will return an error. Service logs are not exposed via the API.

Server Coolify MCP Server kof70/coolify-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_service_logs does on Coolify MCP Server

AI agents call get_service_logs to retrieve information from Coolify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_service_logs needs a policy

Despite the tool's intended purpose being to read/retrieve service logs (a Read operation), the description explicitly states the endpoint is not available and will return an error. This makes it functionally inert with no practical security impact.

From the tool's definition Tool description states it retrieves logs from a service ('Get logs from a service'). The note clarifies the endpoint is not actually available in the Coolify API and returns an error, meaning it has no functional capability to perform any action.

Questions about get_service_logs

What does the get_service_logs tool do? +

Get logs from a service. NOTE: This endpoint is not available in Coolify API and will return an error. Service logs are not exposed via the API. It is categorised as a Read tool in the Coolify MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_service_logs? +

Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for get_service_logs: 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.

What risk level is get_service_logs? +

get_service_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_service_logs? +

Yes. Add a rate_limit block to the get_service_logs 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.

How do I block get_service_logs completely? +

Set action: deny in the PolicyLayer policy for get_service_logs. 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.

What MCP server provides get_service_logs? +

get_service_logs is provided by the Coolify MCP Server MCP server (kof70/coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.