AI agents call read-query to retrieve information from SQLite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a SQLite database for information retrieval with no side effects. It has no destructive, financial, or code execution semantics—it only reads and returns data. Severity is low as misuse only exposes existing data without causing modification or harm. Confidence is high due to the explicit 'read-' prefix and the clear data analysis context of the server.
From the tool's definition Tool is named 'read-query' and the server description indicates it 'provides database interaction capabilities through SQLite, enabling users to run SQL queries'.
Documented attack patterns abuse exactly the kind of access read-query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SQLite MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read-query:
{
"version": "1",
"default": "deny",
"tools": {
"read-query": {}
}
}read-query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
read-query. It is categorised as a Read tool in the SQLite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQLite MCP Server MCP server in PolicyLayer and add a rule for read-query: 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 SQLite MCP Server. Nothing to install.
read-query 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 read-query 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 read-query. 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.
read-query is provided by the SQLite MCP Server MCP server (jacksteamdev/mcp-sqlite-bun-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SQLite MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 SQLite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.