Get overall statistics for log files
AI agents call get_log_stats 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 and computes statistics from log files without modifying, deleting, or executing operations. It is a read-only analytical operation with minimal security risk, as it only queries existing data. The low severity reflects that exposing log statistics has limited blast radius—the worst outcome is information disclosure about system activity.
From the tool's definition Tool name 'get_log_stats' and description 'Get overall statistics for log files' indicates retrieval and analysis of existing log data. No modification, deletion, or execution of external operations is implied.
Attacks that exploit this kind of access
Get overall statistics for log files. 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 get_log_stats: 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.
get_log_stats 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_stats 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_stats. 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_stats 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 →