turn_screen_on · AutoBot MCP: Risk & Policy

WHAT IT DOES

What turn_screen_on does on AutoBot MCP

AI agents invoke turn_screen_on to trigger actions in AutoBot MCP. 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 turn_screen_on needs a policy

Turning on the screen is an external operation that changes the device's physical state. It is not purely reading data, nor does it destroy or write persistent data. It executes a device control action, fitting the Execute category. Misuse could be used to wake a device for further unauthorized interactions, making severity medium.

From the tool's definition 'Turn on the screen' — triggers a physical device state change on a remote Android device via AutoBot API

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

turn_screen_on Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "turn_screen_on": {
      "limits": [
        {
          "counter": "turn_screen_on_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 AutoBot MCP, so you can run agents against it safely.

FAQ

Questions about turn_screen_on

What does the turn_screen_on tool do? +

Turn on the screen. It is categorised as a Execute tool in the AutoBot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on turn_screen_on? +

Register the AutoBot MCP server in PolicyLayer and add a rule for turn_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 AutoBot MCP. Nothing to install.

What risk level is turn_screen_on? +

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

Can I rate-limit turn_screen_on? +

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

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

turn_screen_on is provided by the AutoBot MCP server (yz0903/autobot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.