adb_pull_data

Pull files or directories from the device to local storage.

SERVERAndroid Forensics ADB MCP Server SOURCE0x-professor/droidforensics-suite

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

WHAT IT DOES

What adb_pull_data does on Android Forensics ADB MCP Server

AI agents call adb_pull_data to retrieve information from Android Forensics ADB MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why adb_pull_data is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_pull_data safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Android Forensics ADB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_pull_data, this is the rule to start with:

adb_pull_data Allowed

adb_pull_data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_pull_data": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Android Forensics ADB MCP Server, apply this rule, and every adb_pull_data call is checked against it from then on.

FAQ

Questions about adb_pull_data

What does the adb_pull_data tool do? +

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.

How do I enforce a policy on adb_pull_data? +

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.

What risk level is adb_pull_data? +

adb_pull_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_pull_data? +

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.

How do I block adb_pull_data completely? +

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.

What MCP server provides adb_pull_data? +

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.

KEEP EXPLORING

More on Android Forensics ADB MCP Server, and thousands of servers like it.

This server

All 58 Android Forensics ADB MCP Server tools →

Across the catalogue

collect_devtools_data on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →