Execute a SELECT query to read data from the database
AI agents call query_database to retrieve information from MCP-Turso without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is restricted to SELECT queries, which retrieve data without modification, deletion, or execution of arbitrary code. The server description confirms the tool supports only 'SELECT query execution' alongside table listing and schema retrieval.
From the tool's definition Tool description explicitly states 'Execute a SELECT query to read data from the database' — SELECT queries are read-only operations with no side effects.
Documented attack patterns abuse exactly the kind of access query_database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Turso, and nothing reaches the server without passing your rules. This is the rule we recommend for query_database:
{
"version": "1",
"default": "deny",
"tools": {
"query_database": {}
}
}query_database 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.
Execute a SELECT query to read data from the database. It is categorised as a Read tool in the MCP-Turso MCP Server, which means it retrieves data without modifying state.
Register the MCP-Turso MCP server in PolicyLayer and add a rule for query_database: 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-Turso. Nothing to install.
query_database 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_database 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_database. 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_database is provided by the MCP-Turso MCP server (nbbaier/mcp-turso). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Turso, 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.
4 MCP-Turso tools catalogued and risk-classified — across an index of 43,000+ MCP servers.