adb_pull

Pull a file from the device into the workspace directory. Risk 3.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/adb-pull.md

WHAT IT DOES

What adb_pull does on LocalAnt

AI agents use adb_pull to create or update resources in LocalAnt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LocalAnt environment.

RISK

Why adb_pull is rated Medium

This tool copies a file from an Android device into the local workspace directory. It creates/writes a new file on the host filesystem, which is a Write operation. While 'pulling' sounds like Read, the side effect is writing data to the local system. It is reversible (the file can be deleted), so it does not qualify as Destructive.

From the tool's definition Pull a file from the device into the workspace directory

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_pull safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, 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 Rate-limited

adb_pull stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_pull": {
      "limits": [
        {
          "counter": "adb_pull_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_pull call is checked against it from then on.

FAQ

Questions about adb_pull

What does the adb_pull tool do? +

Pull a file from the device into the workspace directory. Risk 3. It is categorised as a Write tool in the LocalAnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on adb_pull? +

Register the LocalAnt 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 LocalAnt. Nothing to install.

What risk level is adb_pull? +

adb_pull is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit adb_pull? +

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.

How do I block adb_pull completely? +

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.

What MCP server provides adb_pull? +

adb_pull is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →