Pull a file from the device
AI agents call pull_file to retrieve information from Enhanced ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool extracts data from the device but does not create, modify, delete, or execute anything. It is purely a read operation. Severity is low because while pulled files could theoretically contain sensitive data, the tool itself is a standard diagnostic/backup operation in ADB workflows, and harm depends entirely on what the user does with the retrieved file, not on the tool's inherent capabilities.
From the tool's definition The tool 'pull_file' with description 'Pull a file from the device' retrieves file data from an Android device via ADB without modifying or deleting it. Pulling files is a retrieval operation with no side effects on the source device.
Attacks that exploit this kind of access
Pull a file from the device. It is categorised as a Read tool in the Enhanced ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced ADB MCP Server 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 Enhanced ADB MCP Server. 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 Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). 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 →