turn_screen_off · AutoBot MCP: Risk & Policy

WHAT IT DOES

What turn_screen_off does on AutoBot MCP

AI agents invoke turn_screen_off 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_off needs a policy

This tool triggers an external hardware operation on an Android device — turning off its screen. While not destructive or financial, it executes a device-level action that changes the device's state. The device remains active, so it's reversible, but it's an operation that affects the physical device's behavior rather than a simple data read or write.

From the tool's definition Turn off the screen (device remains active for control/casting)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

turn_screen_off Rate-limited

turn_screen_off 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_off": {
      "limits": [
        {
          "counter": "turn_screen_off_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_off

What does the turn_screen_off tool do? +

Turn off the screen (device remains active for control/casting). 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_off? +

Register the AutoBot MCP server in PolicyLayer and add a rule for turn_screen_off: 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_off? +

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

Can I rate-limit turn_screen_off? +

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

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

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