Get list of available log files with metadata
AI agents call get_log_files to retrieve information from Local Logs 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 metadata about log files—a non-destructive read operation. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. The blast radius of misuse is minimal; at worst, an agent gains visibility into available logs, which is informational only. Classified as Read with low severity.
From the tool's definition Tool name 'get_log_files' and description 'Get list of available log files with metadata' indicate a retrieval operation that queries and lists data without modification or execution of external operations.
Attacks that exploit this kind of access
Get list of available log files with metadata. It is categorised as a Read tool in the Local Logs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Local Logs MCP Server MCP server in PolicyLayer and add a rule for get_log_files: 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 Local Logs MCP Server. Nothing to install.
get_log_files 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 get_log_files 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 get_log_files. 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.
get_log_files is provided by the Local Logs MCP Server MCP server (mariosss/local-logs-mcp-server). 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 →