stop_emulator · Android Emulator MCP: Risk & Policy

WHAT IT DOES

What stop_emulator does on Android Emulator

AI agents invoke stop_emulator to trigger actions in Android Emulator. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why stop_emulator needs a policy

Stopping an emulator is an executable action that triggers control over an external system (the Android emulator process). While reversible (the emulator can be restarted), it represents active manipulation of a running service rather than data retrieval or modification. This falls into the Execute category as it triggers an external operation whose effects depend on which emulator instance is targeted.

From the tool's definition Tool name: 'stop_emulator'. Description: 'Stop a running emulator.' This action terminates a running process/service, which is a system-level operation that affects external state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_emulator Rate-limited

stop_emulator stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_emulator": {
      "limits": [
        {
          "counter": "stop_emulator_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Emulator, so you can run agents against it safely.

FAQ

Questions about stop_emulator

What does the stop_emulator tool do? +

Stop a running emulator. It is categorised as a Execute tool in the Android Emulator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_emulator? +

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

What risk level is stop_emulator? +

stop_emulator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_emulator? +

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

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

stop_emulator is provided by the Android Emulator MCP server (janjetze/android-emulator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.