AI agents use push_file to create or update resources in Adb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adb environment.
This tool creates or modifies files on a remote Android device, which is a reversible Write operation. While not immediately destructive, it has high severity because an AI agent could push malicious APKs, modify system files, inject malware, or overwrite critical application data on connected devices. The blast radius is significant in an Android environment where file permissions and system integrity matter.
From the tool's definition Tool name 'push_file' combined with server description 'file transfer' indicates the tool uploads/transfers files to Android devices.
Documented attack patterns abuse exactly the kind of access push_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for push_file:
{
"version": "1",
"default": "deny",
"tools": {
"push_file": {
"limits": [
{
"counter": "push_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}push_file 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.
将文件推送到设备. It is categorised as a Write tool in the Adb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adb MCP server in PolicyLayer and add a rule for 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. Nothing to install.
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 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 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.
push_file is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, 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.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.