This record as markdown: /tools/io-github-fullread-deepadb/adb-pull.md
What adb_pull does on Deepadb
AI agents call adb_pull 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_pull is rated Low
This tool performs a unidirectional data retrieval operation (device → local storage). It does not modify, delete, or execute anything on the device or local system. While it could potentially extract sensitive data depending on file permissions and what files are accessible, the tool itself is fundamentally a read operation with no side effects.
From the tool's definition 'Pull a file from the device to local filesystem' — retrieves file content from a remote device without modification or deletion.
Attacks that exploit this kind of access
The rule that runs adb_pull 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_pull, this is the rule to start with:
adb_pull 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_pull call is checked against it from then on.
Questions about adb_pull
Pull a file from the device to local filesystem. 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_pull: 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_pull 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_pull 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_pull. 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_pull 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