Get the schema for all tables in the database
AI agents call get_db_schema 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.
This tool only queries database metadata (table schemas) without creating, modifying, deleting, or executing arbitrary code. It has no side effects and poses minimal risk—typical information disclosure limited to structural data. Severity is low because schema information alone does not compromise data integrity or enable unauthorized data access beyond what the server already permits via SELECT queries.
From the tool's definition Tool retrieves schema information ('Get the schema for all tables') with no data modification or execution capabilities described.
Documented attack patterns abuse exactly the kind of access get_db_schema 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 get_db_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_db_schema": {}
}
}get_db_schema 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.
Get the schema for all tables in 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 get_db_schema: 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.
get_db_schema 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 get_db_schema 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 get_db_schema. 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.
get_db_schema 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.