Query logs from a registered source.
AI agents call query_logs to retrieve information from MCP 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 and examines log data from already-registered sources. Querying logs is a non-destructive, read-only operation that does not create, modify, delete, or execute anything. While the broader server includes destructive tools like 'delete_log_source', this specific tool is limited to querying/analyzing existing logs.
From the tool's definition Tool name 'query_logs' combined with description 'Query logs from a registered source' indicates a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Query logs from a registered source. It is categorised as a Read tool in the MCP Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Log Analyzer 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 MCP Log Analyzer. 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 MCP Log Analyzer MCP server (sedwardstx/demomcp). 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 →