List available log files with metadata
AI agents call list_log_files to retrieve information from JSON 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 existing log files without altering them. It is a read-only operation that enumerates available resources. The context of a log management server (with sibling tools like aggregate_logs, get_log_stats, and query_logs) confirms this is a query/discovery function. No side effects or data modification occurs.
From the tool's definition Tool name 'list_log_files' and description 'List available log files with metadata' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
List available log files with metadata. It is categorised as a Read tool in the JSON Logs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JSON Logs MCP Server MCP server in PolicyLayer and add a rule for list_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 JSON Logs MCP Server. Nothing to install.
list_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 list_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 list_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.
list_log_files is provided by the JSON Logs MCP Server MCP server (mfreeman451/json-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 →