Pushes files from the local system to a connected Android device
AI agents use adb_push to create or update resources in Android ADB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android ADB MCP Server environment.
adb_push creates or modifies files on an Android device, which is a Write operation. It is not Read (no retrieval), Destructive (files are not irreversibly deleted), Execute (not running arbitrary commands, though consequences depend on what files are pushed), Financial, or Other.
From the tool's definition Tool name 'adb_push' and description 'Pushes files from the local system to a connected Android device' indicates file transfer that modifies the device's filesystem by adding or overwriting files.
Documented attack patterns abuse exactly the kind of access adb_push gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_push:
{
"version": "1",
"default": "deny",
"tools": {
"adb_push": {
"limits": [
{
"counter": "adb_push_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} adb_push stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Pushes files from the local system to a connected Android device. It is categorised as a Write tool in the Android ADB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android ADB MCP Server MCP server in PolicyLayer and add a rule for adb_push: 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 ADB MCP Server. Nothing to install.
adb_push 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 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. 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 is provided by the Android ADB MCP Server MCP server (landicefu/android-adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android ADB MCP Server, 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.
10 Android ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.