Low Risk

pull_directory

Pull an entire directory from the device recursively.

How to control pull_directory ↓

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 — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why pull_directory needs a policy

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

Documented attack patterns abuse exactly the kind of access pull_directory gives an agent:

How to control pull_directory

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 pull_directory:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pull_directory": {}
  }
}

pull_directory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Android Forensics ADB MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Android Forensics ADB MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.