Fetch logs from local folder; chunk with overlap & save.
AI agents call fetch_local_logs to retrieve information from Log Analyzer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and processes local log data without altering the source logs or creating permanent side effects beyond internal caching/vectorization for analysis. This is a standard read operation that enables downstream querying and analysis. No data is created, modified, deleted, or destroyed in the source system.
From the tool's definition Tool description explicitly states 'Fetch logs from local folder' - a retrieval operation with no modification. The chunking and saving appear to be internal processing steps for the read operation itself, not modifications to the original logs.
Attacks that exploit this kind of access
Fetch logs from local folder; chunk with overlap & save. It is categorised as a Read tool in the Log Analyzer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Log Analyzer MCP Server MCP server in PolicyLayer and add a rule for fetch_local_logs: 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 Analyzer MCP Server. Nothing to install.
fetch_local_logs 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 fetch_local_logs 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 fetch_local_logs. 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.
fetch_local_logs is provided by the Log Analyzer MCP Server MCP server (suriya-ml/log-checker-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 →