Get logs from a deployment
AI agents call coolify.get_deployment_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.
This tool retrieves log data from deployments without side effects. It does not create, modify, delete, execute code, or move resources. While logs may contain sensitive information, the tool itself is a read-only query operation on existing deployment artifacts. The severity is low because log access is primarily informational with no capability to alter system state.
From the tool's definition Tool name includes 'get' and description states 'Get logs from a deployment' - retrieves existing deployment logs without modification or execution.
Attacks that exploit this kind of access
Get logs from a deployment. It is categorised as a Read tool in the Coolify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for coolify.get_deployment_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.
coolify.get_deployment_logs 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 coolify.get_deployment_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.
Set action: deny in the PolicyLayer policy for coolify.get_deployment_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.
coolify.get_deployment_logs is provided by the Coolify MCP Server MCP server (thedurancode/coolify-mcp). 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 →