AI agents call query_log to retrieve information from Mcp Query without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads audit log entries to display them. It has no side effects, does not execute queries against data, and does not modify system state. The blast radius of misuse is minimal — an agent could only view audit history, which may contain metadata about past operations but cannot trigger new operations or alter data. Classification as Read is appropriate.
From the tool's definition Tool name is 'query_log' and description states 'Show recent query audit log entries' — this retrieves and displays historical log data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Show recent query audit log entries. It is categorised as a Read tool in the Mcp Query MCP Server, which means it retrieves data without modifying state.
Register the Mcp Query MCP server in PolicyLayer and add a rule for query_log: 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 Query. Nothing to install.
query_log 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_log 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_log. 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_log is provided by the Mcp Query MCP server (ottimis/mcp-query). 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 →