Query logs within a specific time range
AI agents call query_by_timerange to retrieve information from Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log entries filtered by time range. It has no side effects, does not modify or delete data, does not execute code or system commands, and does not involve financial transactions. It is a straightforward read operation consistent with log search and analysis use cases.
From the tool's definition Tool name 'query_by_timerange' and description 'Query logs within a specific time range' indicate retrieval of log data without modification.
Attacks that exploit this kind of access
Query logs within a specific time range. It is categorised as a Read tool in the Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Log Analyzer MCP server in PolicyLayer and add a rule for query_by_timerange: 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. Nothing to install.
query_by_timerange 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_by_timerange 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_by_timerange. 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_by_timerange is provided by the Log Analyzer MCP server (yufeizhou666/my_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 →