Returns the content of a specific log file from $XDG_RUNTIME_DIR/log. Use this to inspect runtime logs when debugging errors or investigating problems. For large files, use read_log_paginated instead.
AI agents call get_log_content to retrieve information from Log 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 and displays log file contents for inspection and debugging purposes. It performs no side effects, creates no data, executes no code, and deletes nothing. The low severity reflects that log files typically contain non-sensitive debugging information in standard runtime directories, with minimal blast radius if misused by an agent (worst case: reading existing logs).
From the tool's definition Tool name 'get_log_content' and description 'Returns the content of a specific log file' indicates retrieval of data with no modification or execution capability.
Attacks that exploit this kind of access
Returns the content of a specific log file from $XDG_RUNTIME_DIR/log. Use this to inspect runtime logs when debugging errors or investigating problems. For large files, use read_log_paginated instead. It is categorised as a Read tool in the Log MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Log MCP Server MCP server in PolicyLayer and add a rule for get_log_content: 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 Log MCP Server. Nothing to install.
get_log_content 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_log_content 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_log_content. 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_log_content is provided by the Log MCP Server MCP server (thhart/log-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_log_content is one line of Log MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →