screen_on

THE RISK

High Risk

This tool triggers an external operation on a physical/virtual Android device (turning the screen on). It causes a side effect on the device state but is reversible and low-impact — the screen can be turned off again. It fits Execute as it triggers an external device operation, with low severity since it merely wakes the screen.

From the tool's definition Turn the device screen on. Useful when the device has gone to sleep during automated testing.

Documented attack patterns abuse exactly the kind of access screen_on gives an agent:

HOW TO CONTROL SCREEN_ON

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for screen_on:

policy.json

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

screen_on 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.

Create a free account and register MCP Android Agent — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More MCP Android Agent tools

Destructive clear_app_data Clear all data and cache for a specific app. This is equivalent to Execute start_app Launch an Android application by its package name with optional wait for the app to appear Execute stop_all_apps Force stop all running applications on the device to free up memory and start with a clean Execute stop_app Force stop an Android application by its package name. Useful for closing apps that are mi Execute wait_activity Wait for a specific Android activity to appear on the screen. Useful for navigation verifi Execute wait_for_element Wait for a UI element to appear on the screen. Essential for handling loading screens, ani Execute wait_for_screen_on Wait until the device screen is turned on. Useful for asynchronous operations where screen Execute click Click on a UI element identified by text, resource ID, or content description. Supports mu

All 28 MCP Android Agent tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in MCP Android Agent → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the screen_on tool do? +

Turn the device screen on. Useful when the device has gone to sleep during automated testing. It is categorised as a Execute tool in the MCP Android Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screen_on? +

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

What risk level is screen_on? +

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

Can I rate-limit screen_on? +

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

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

screen_on is provided by the MCP Android Agent MCP server (nim444/mcp-android-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Android Agent tool call.

Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP ANDROID AGENT →

Free to start. No card required.

28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT SCREEN_ON ON MCP ANDROID AGENT DOES

// THE RISK

// HOW TO CONTROL SCREEN_ON

// EXPLORE