Searches a log file using regex pattern and returns matching lines with surrounding context. Supports token-based pagination to respect AI context limits.
AI agents call search_log_file 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 performs a search query against log files and returns results. It retrieves and displays existing log data without modifying, deleting, or executing any operations. The use of regex for searching is a standard read operation on log files. There are no side effects, reversible changes, code execution, or data destruction involved.
From the tool's definition Tool description states it 'Searches a log file using regex pattern and returns matching lines with surrounding context.' The verb 'searches' and 'returns' indicate data retrieval only.
Attacks that exploit this kind of access
Searches a log file using regex pattern and returns matching lines with surrounding context. Supports 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 search_log_file: 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.
search_log_file 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 search_log_file 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 search_log_file. 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.
search_log_file 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 →