AI agents use adb_push 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.
adb_push transfers files to an Android device, modifying the device's filesystem. This is a Write operation because it creates/modifies data on the target system. The severity is high because an attacker with access could push malicious executables, configuration files, or other code to compromise the device. However, it is not Destructive (reversible) or Execute (depends on what is pushed, not the tool itself).
From the tool's definition Tool name 'adb_push' is the ADB command for transferring files TO an Android device. In the Android Debug Bridge (ADB) context, 'push' uploads/transfers files from a computer to the device filesystem.
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 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.
adb_push. 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: 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 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 ADB MCP Server MCP server (srmorete/adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 ADB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 ADB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.