Pulls files from a connected Android device to the local system
AI agents call adb_pull to retrieve information from Android ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
adb_pull is a read operation that transfers files from an Android device to the local system. While it retrieves data (Read category), the severity is rated high rather than low because: (1) it can access sensitive device data including credentials, private messages, photos, and personal files; (2) the blast radius is significant if an AI agent is misdirected to exfiltrate confidential information; (3) it requires…
From the tool's definition Tool name and description: 'Pulls files from a connected Android device to the local system' — retrieval of data from device to local system without modification of the source.
Documented attack patterns abuse exactly the kind of access adb_pull gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_pull:
{
"version": "1",
"default": "deny",
"tools": {
"adb_pull": {}
}
} adb_pull 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.
Pulls files from a connected Android device to the local system. It is categorised as a Read tool in the Android ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Android ADB MCP Server 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 Android ADB MCP Server. Nothing to install.
adb_pull 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 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. 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 is provided by the Android ADB MCP Server MCP server (landicefu/android-adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android 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.
10 Android ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.