Quickly finds error lines in a log file by matching common error patterns (ERROR, Exception, FATAL, Failed, Traceback, panic, etc.). Ideal for quick diagnostics.
AI agents call find_errors 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 filters log data based on error patterns. It has no side effects, does not execute arbitrary code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could only retrieve sensitive information that may already be in logs, which is the tool's intended purpose. Therefore, it is categorized as Read with low severity.
From the tool's definition Tool description states it 'finds error lines in a log file by matching common error patterns' and is for 'quick diagnostics'. The tool performs pattern matching and searching within log files without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Quickly finds error lines in a log file by matching common error patterns (ERROR, Exception, FATAL, Failed, Traceback, panic, etc.). Ideal for quick diagnostics. 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 find_errors: 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.
find_errors 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 find_errors 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 find_errors. 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.
find_errors 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 →