Push a file from local system to device
AI agents use adb_push_file to create or update resources in ADB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ADB MCP Server environment.
The tool creates or modifies files on an Android device, which is reversible (files can be deleted or overwritten). This is a Write-category action with high severity due to potential for malicious file injection, installation of malware, or corruption of device functionality. The blast radius is significant in an automated context where an AI agent could push arbitrary files to a device without user oversight.
From the tool's definition Tool name 'adb_push_file' and description 'Push a file from local system to device' indicate file creation/modification on a remote Android device. This is a Write operation—it transfers and creates/modifies files on the target device.
Attacks that exploit this kind of access
Push a file from local system to device. It is categorised as a Write tool in the ADB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_push_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 MCP Server. Nothing to install.
adb_push_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_push_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 adb_push_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.
adb_push_file is provided by the ADB MCP Server MCP server (richard0913/adb-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 →