AI agents call query_history to retrieve information from Querywise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists past query execution records. It performs a read-only operation with no side effects—it neither modifies, deletes, nor executes any queries itself. The blast radius of misuse is minimal; an agent could only view historical query metadata, posing no risk to data integrity or system operations. Classified as Read with low severity.
From the tool's definition Tool name 'query_history' and description 'List recent query executions for a connection, newest first' indicate retrieval of historical data with no modification or deletion of records.
Attacks that exploit this kind of access
List recent query executions for a connection, newest first. It is categorised as a Read tool in the Querywise MCP Server, which means it retrieves data without modifying state.
Register the Querywise MCP server in PolicyLayer and add a rule for query_history: 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 Querywise. Nothing to install.
query_history 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_history 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_history. 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_history is provided by the Querywise MCP server (kosminus/querywise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
query_history is one line of Querywise's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →