pull_directory

Pull an entire directory from the device recursively.

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 →

This record as markdown: /tools/0x-professor-droidforensics-suite/pull-directory.md

WHAT IT DOES

What pull_directory does on Android Forensics ADB MCP Server

AI agents call pull_directory 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 pull_directory is rated Low

This tool retrieves data from an Android device without modifying, deleting, or executing operations on it. It is a Read operation because it acquires forensic artifacts for analysis.

From the tool's definition Tool description states 'Pull an entire directory from the device recursively.' The verb 'pull' in ADB context means to retrieve/extract data from the device to the investigator's system.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pull_directory 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 pull_directory, this is the rule to start with:

pull_directory Allowed

pull_directory 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": {
    "pull_directory": {}
  }
}

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 pull_directory call is checked against it from then on.

FAQ

Questions about pull_directory

What does the pull_directory tool do? +

Pull an entire directory from the device recursively. 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 pull_directory? +

Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for pull_directory: 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 pull_directory? +

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

Can I rate-limit pull_directory? +

Yes. Add a rate_limit block to the pull_directory 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 pull_directory completely? +

Set action: deny in the PolicyLayer policy for pull_directory. 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 pull_directory? +

pull_directory 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

The MCP Attack Database →

Guides

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