adb_grep
Search file contents on the device by text pattern. Uses fixed-string matching by default (no regex injection risk). Supports recursive directory search with depth control and result capping. For filename searches, use adb_find instead.
This record as markdown: /tools/io-github-fullread-deepadb/adb-grep.md
What adb_grep does on Deepadb
AI agents call adb_grep 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_grep is rated Low
This tool retrieves and queries file contents from an Android device without modifying, executing, or deleting anything. It is purely informational with safe matching behavior (fixed-string, no regex). The blast radius of misuse is minimal—worst case, an agent could infer sensitive information already present on the device, but cannot alter device state. This is a classic Read operation.
From the tool's definition Tool description explicitly states 'Search file contents on the device by text pattern' and 'uses fixed-string matching by default (no regex injection risk)'. No write, delete, execute, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs adb_grep 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_grep, this is the rule to start with:
adb_grep 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_grep call is checked against it from then on.
Questions about adb_grep
Search file contents on the device by text pattern. Uses fixed-string matching by default (no regex injection risk). Supports recursive directory search with depth control and result capping. For filename searches, use adb_find instead. 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_grep: 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_grep 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_grep 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_grep. 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_grep 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