push_file_to_device · MCP Emulator Controller MCP

WHAT IT DOES

What push_file_to_device does on MCP Emulator Controller

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

WHY IT NEEDS A POLICY

Why push_file_to_device needs a policy

This tool creates or modifies files on a target device, which is a Write operation. Severity is high because an agent could push malicious files, overwrite critical system files, install unauthorized APKs, or inject data that compromises the device or running applications. The blast radius depends on what files are pushed and where, but the capability to arbitrarily modify device storage poses significant risk.

From the tool's definition Tool name 'push_file_to_device' and description 'Push file to device' indicate file transfer capability to an Android emulator or connected device. This modifies the device filesystem by adding or updating files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_file_to_device Rate-limited

push_file_to_device 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_to_device": {
      "limits": [
        {
          "counter": "push_file_to_device_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 MCP Emulator Controller, so you can run agents against it safely.

FAQ

Questions about push_file_to_device

What does the push_file_to_device tool do? +

Push file to device. It is categorised as a Write tool in the MCP Emulator Controller 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_to_device? +

Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for push_file_to_device: 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 MCP Emulator Controller. Nothing to install.

What risk level is push_file_to_device? +

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

Can I rate-limit push_file_to_device? +

Yes. Add a rate_limit block to the push_file_to_device 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_to_device completely? +

Set action: deny in the PolicyLayer policy for push_file_to_device. 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_to_device? +

push_file_to_device is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.