Reads a specific range of lines from a log file. Uses token-based pagination to respect AI context limits.
AI agents call read_log_range 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 log file content within a specified line range without modifying, deleting, or executing anything. It is purely informational, supporting the debugging and troubleshooting use case described in the server's purpose. The token-based pagination is a safety mechanism to respect context limits, not a risk factor. There are no side effects or state changes from invoking this tool.
From the tool's definition Tool description explicitly states it 'Reads a specific range of lines from a log file' with token-based pagination. The verb 'Reads' and the lack of any modification, deletion, or execution capability clearly indicate a read-only operation.
Attacks that exploit this kind of access
Reads a specific range of lines from a log file. Uses token-based pagination to respect AI context limits. 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 read_log_range: 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.
read_log_range 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 read_log_range 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 read_log_range. 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.
read_log_range 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.
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 →