AI agents call pull_file to retrieve information from Adb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/downloads files from a remote Android device. It is a read-only operation with no side effects on the device state. While it could potentially expose sensitive data if misused by an agent, the tool itself performs only data retrieval (analogous to 'download_file' mentioned in sibling tools).
From the tool's definition Tool name 'pull_file' and description '从设备拉取文件' (pull file from device) indicate retrieval of data from an Android device without modification or deletion.
Documented attack patterns abuse exactly the kind of access pull_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for pull_file:
{
"version": "1",
"default": "deny",
"tools": {
"pull_file": {}
}
}pull_file 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.
从设备拉取文件. It is categorised as a Read tool in the Adb MCP Server, which means it retrieves data without modifying state.
Register the Adb MCP server in PolicyLayer and add a rule for pull_file: 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 Adb. Nothing to install.
pull_file 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 pull_file 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 pull_file. 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.
pull_file is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, 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.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.