push_file · Android Device MCP: Risk & Policy

WHAT IT DOES

What push_file does on Android Device

AI agents use push_file to create or update resources in Android Device — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android Device environment.

WHY IT NEEDS A POLICY

Why push_file needs a policy

The tool creates or modifies data on the target Android device by copying files to it. This is reversible (files can be deleted), so it is Write rather than Destructive. The severity is high because an AI agent misusing this could push malicious files, scripts, or data that compromises the device, installs unwanted software, or alters system state.

From the tool's definition Tool description states it 'Push or copy files from a given directory on local machine to an Android device'. This is a write operation that modifies the Android device's filesystem by adding or overwriting files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_file Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_file": {
      "limits": [
        {
          "counter": "push_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Android Device, so you can run agents against it safely.

FAQ

Questions about push_file

What does the push_file tool do? +

Push or copy files from a given directory on local machine to an Android device using its serial number. It is categorised as a Write tool in the Android Device MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_file? +

Register the Android Device 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 Android Device. Nothing to install.

What risk level is push_file? +

push_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit push_file? +

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.

How do I block push_file completely? +

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.

What MCP server provides push_file? +

push_file is provided by the Android Device MCP server (prashant1507/android-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.