Search and filter log entries across log files
AI agents call query_logs 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 filters existing log entries—a classic read operation with no side effects. The sibling tools (aggregate_logs, get_log_stats, list_log_files) further confirm this server is for log inspection and analysis only. Severity is low because read access to logs, while sensitive in some contexts, does not enable data modification, deletion, or code execution.
From the tool's definition Tool name is 'query_logs' with description 'Search and filter log entries across log files'. The verbs 'search' and 'filter' indicate read-only operations that retrieve and query log data without modifying, deleting, or executing arbitrary code.
Attacks that exploit this kind of access
Search and filter log entries across 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 query_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 JSON Logs MCP Server. Nothing to install.
query_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 query_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 query_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.
query_logs 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 →