Pushes a file from the local machine to the connected Android device. Requires local and remote parameters, which are the paths of the file on the local machine and the device respectively.
AI agents use push_file to create or update resources in Ultimate Android MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ultimate Android MCP environment.
The tool creates or uploads files to an Android device, which is a reversible write operation. It's categorized as Write rather than Execute because the tool itself performs file transfer, not code execution (though uploaded files could subsequently be executed).
From the tool's definition Tool description states it 'Pushes a file from the local machine to the connected Android device' using local and remote path parameters. This is a file creation/upload operation that modifies the target device's filesystem.
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 Ultimate Android MCP, 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.
Pushes a file from the local machine to the connected Android device. Requires local and remote parameters, which are the paths of the file on the local machine and the device respectively. It is categorised as a Write tool in the Ultimate Android MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ultimate Android 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 Ultimate Android MCP. 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 Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ultimate Android MCP, 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.
35 Ultimate Android MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.