Reads the end of a log file (like Unix
AI agents call tail_log 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 data from log files without side effects. It performs a read-only operation analogous to the Unix 'tail' command, which outputs the final lines of a file. All sibling tools (find_errors, get_log_content, head_log, list_log_files, read_log_paginated, read_log_range, search_log_file) are similarly read-only inspection utilities. No data is created, modified, deleted, or executed—only queried.
From the tool's definition Tool name 'tail_log' and description 'Reads the end of a log file (like Unix' indicate retrieval/querying of existing log file content with no modifications, deletions, or external operations triggered.
Attacks that exploit this kind of access
Reads the end of a log file (like Unix. 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 tail_log: 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.
tail_log 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 tail_log 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 tail_log. 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.
tail_log 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 →