Get information about the SQLite database including path, existence, size, and table count
AI agents call db_info to retrieve information from Mcp Sqlite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports database metadata. It has no side effects—it does not create, modify, delete, or execute operations on data. It is purely informational, making it a Read category risk with low severity since the blast radius of misuse is minimal (an agent could at most learn about database structure and size, which is already visible to any connected user).
From the tool's definition Tool description states it retrieves information about the SQLite database (path, existence, size, table count). The name 'db_info' and description indicate a query operation that gathers metadata without modifying data.
Attacks that exploit this kind of access
Get information about the SQLite database including path, existence, size, and table count. It is categorised as a Read tool in the Mcp Sqlite MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sqlite MCP server in PolicyLayer and add a rule for db_info: 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 Sqlite. Nothing to install.
db_info 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 db_info 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 db_info. 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.
db_info is provided by the Mcp Sqlite MCP server (mcp-sqlite). 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 →