get_logs

What get_logs does on Ncp

AI agents call get_logs to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_logs is rated Low

This tool retrieves log information from a pod without causing side effects, modification of data, or execution of arbitrary code. It is a read-only operation that queries existing log data. The severity is low as log access itself poses minimal risk unless logs contain highly sensitive information, but the action itself is non-destructive and non-executable.

From the tool's definition Tool name 'get_logs' and description 'Get logs from a pod' indicate retrieval of existing log data with no modification or execution of operations.

The rule that runs get_logs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_logs, this is the rule to start with:

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

Questions about get_logs