Pull files or directories from the device to local storage.
AI agents call adb_pull_data to retrieve information from Android Forensics ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this is a forensic tool operating on Android devices, the adb_pull_data function performs a read-only operation: it retrieves and copies data from the device to local storage without modifying, deleting, or executing anything on the source device. The risk is low because the operation is non-destructive and reversible, with effects limited to the investigator's local environment.
From the tool's definition Tool description states 'Pull files or directories from the device to local storage' - a retrieval operation with no modification of source data. The term 'pull' in ADB contexts means copying/reading data without alterations.
Documented attack patterns abuse exactly the kind of access adb_pull_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Forensics ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_pull_data:
{
"version": "1",
"default": "deny",
"tools": {
"adb_pull_data": {}
}
}adb_pull_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Pull files or directories from the device to local storage. It is categorised as a Read tool in the Android Forensics ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for adb_pull_data: 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 Android Forensics ADB MCP Server. Nothing to install.
adb_pull_data 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_data 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_data. 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_data is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Forensics ADB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
58 Android Forensics ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.