adb_sqlite_inspect
Safely inspect a Room or SQLite database inside an installed app. Lists package databases, shows schema, or executes one validated read-only query. Requires a debuggable app (run-as) or root; uses device sqlite3 when available and otherwise a bounded read-only host snapshot.
This record as markdown: /tools/io-github-fullread-deepadb/adb-sqlite-inspect.md
What adb_sqlite_inspect does on Deepadb
AI agents call adb_sqlite_inspect to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_sqlite_inspect is rated Low
Tool retrieves database schema and executes read-only queries; no data modification or destruction. Medium severity due to potential access to sensitive app data.
From the tool's definition inspect, validated read-only query, executes one validated read-only query
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_sqlite_inspect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_sqlite_inspect, this is the rule to start with:
adb_sqlite_inspect is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_sqlite_inspect call is checked against it from then on.
Questions about adb_sqlite_inspect
Safely inspect a Room or SQLite database inside an installed app. Lists package databases, shows schema, or executes one validated read-only query. Requires a debuggable app (run-as) or root; uses device sqlite3 when available and otherwise a bounded read-only host snapshot. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_sqlite_inspect: 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 Deepadb. Nothing to install.
adb_sqlite_inspect 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 adb_sqlite_inspect 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 adb_sqlite_inspect. 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.
adb_sqlite_inspect is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue