start_screen_record · Enhanced ADB MCP Server MCP

WHAT IT DOES

What start_screen_record does on Enhanced ADB MCP Server

AI agents invoke start_screen_record to trigger actions in Enhanced ADB MCP Server. 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 start_screen_record needs a policy

Screen recording is an Execute-category action because it actively triggers and controls device operations (recording initiation), rather than passively reading data (Read) or modifying stored data (Write/Destructive). While the action is reversible (stopping the recording, deleting the file), the core operation is procedural control of the device.

From the tool's definition Tool is 'start_screen_record' which initiates a continuous screen recording action on an Android device. This is an operational/procedural command that triggers external device behavior with effects dependent on timing and device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_screen_record Rate-limited

start_screen_record 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": {
    "start_screen_record": {
      "limits": [
        {
          "counter": "start_screen_record_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 Enhanced ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about start_screen_record

What does the start_screen_record tool do? +

Start recording the screen. Max duration is 180 seconds. It is categorised as a Execute tool in the Enhanced ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_screen_record? +

Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for start_screen_record: 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 Enhanced ADB MCP Server. Nothing to install.

What risk level is start_screen_record? +

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

Can I rate-limit start_screen_record? +

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

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

start_screen_record is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.