Pull or copy files from a given directory on an Android device using its serial number.
AI agents call pull_file to retrieve information from Android Device without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation as it retrieves data from the Android device without modifying, creating, or deleting anything. However, severity is medium rather than low because an attacker with this tool could exfiltrate sensitive data (credentials, private keys, personal files, app data) from an Android device if misused by an AI agent without proper access controls.
From the tool's definition pull_file description states it 'Pull or copy files from a given directory on an Android device' — a retrieval operation with no side effects on the device state. The tool only reads and transfers file contents.
Attacks that exploit this kind of access
Pull or copy files from a given directory on an Android device using its serial number. It is categorised as a Read tool in the Android Device MCP Server, which means it retrieves data without modifying state.
Register the Android Device 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 Android Device. 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 Android Device MCP server (prashant1507/android-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →