List all SQLite database files (.db, .sqlite, .sqlite3) in the specified directory.
AI agents call list_databases 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 retrieves metadata about available database files in a directory. It performs a directory listing operation without querying data, modifying files, executing SQL, or causing side effects. The blast radius of misuse is minimal—an agent could discover which databases exist, but cannot access their contents, modify them, or trigger external operations.
From the tool's definition Tool name is 'list_databases' and description states it 'List[s] all SQLite database files' — a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
List all SQLite database files (.db, .sqlite, .sqlite3) in the specified directory. 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 list_databases: 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.
list_databases 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 list_databases 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 list_databases. 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.
list_databases is provided by the SQLite MCP Server MCP server (stevefordev/sqlite-mcp). 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 →