get_application_logs

A read tool on the Coolify MCP server.

SERVERCoolify SOURCEcoolify-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/get-application-logs.md

WHAT IT DOES

What get_application_logs does on Coolify

AI agents call get_application_logs 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.

RISK

Why get_application_logs is rated Low

This tool retrieves log data for read-only purposes. Getting logs is a non-destructive query operation that does not modify state, execute arbitrary code, delete data, or commit financial transactions. It poses minimal security risk as an information disclosure concern only if logs contain sensitive data, but the action itself is purely informational.

From the tool's definition Tool name is 'get_application_logs' and description states 'Get application logs' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_application_logs 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_application_logs, this is the rule to start with:

get_application_logs Allowed

get_application_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_application_logs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every get_application_logs call is checked against it from then on.

FAQ

Questions about get_application_logs

What does the get_application_logs tool do? +

get_application_logs is a read tool on the Coolify MCP server. It is categorised as a Read tool in the Coolify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_application_logs? +

Register the Coolify MCP server in PolicyLayer and add a rule for get_application_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. Nothing to install.

What risk level is get_application_logs? +

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

Can I rate-limit get_application_logs? +

Yes. Add a rate_limit block to the get_application_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_application_logs completely? +

Set action: deny in the PolicyLayer policy for get_application_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_application_logs? +

get_application_logs 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.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →