Pulls a file from the connected Android device to the local machine. Requires remote and local parameters, which are the paths of the file on the device and the local machine respectively.
AI agents call pull_file to retrieve information from Ultimate Android MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it retrieves file contents from a remote device without altering, deleting, or executing anything. The file transfer is a unidirectional copy that creates local data without side effects on the device.
From the tool's definition Tool description explicitly states it 'Pulls a file from the connected Android device to the local machine' - a retrieval operation with no modification or deletion of data.
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 Ultimate Android MCP, 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.
Pulls a file from the connected Android device to the local machine. Requires remote and local parameters, which are the paths of the file on the device and the local machine respectively. It is categorised as a Read tool in the Ultimate Android MCP MCP Server, which means it retrieves data without modifying state.
Register the Ultimate Android 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 Ultimate Android MCP. 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 Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ultimate Android MCP, 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.
35 Ultimate Android MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.