// SCAN REPORT

AutoBot MCP

44 tools. 25 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 4 Jul 2026

25 can modify or destroy data

19 read-only

44 tools total

Community server · catalogue entry verified 04/07/2026

How to control AutoBot MCP ↓

TOOL MAP

What AutoBot MCP exposes to your agents

Read (19) Write / Execute (22) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous AutoBot MCP tools

Destructive · High clear_app_data Clearing app data permanently removes user data, preferences, cache, and settings associated with an application. Destructive · High delete_contact This tool irreversibly deletes personal data (contacts) with no undo capability. Destructive · High delete_file Deletion is an irreversible operation that destroys data. Execute · High execute_adb_shell_command This is an Execute tool because it runs arbitrary ADB commands whose effects depend entirely on the arguments provided.

25 of AutoBot MCP's 44 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control AutoBot MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and AutoBot MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_app_data": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "disable_screen_keep_alive": {
    "limits": [
      {
        "counter": "disable_screen_keep_alive_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_clipboard_text": {
    "limits": [
      {
        "counter": "get_clipboard_text_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register AutoBot MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON AUTOBOT →

Instant setup, no code required.

FULL CATALOGUE

All 44 AutoBot MCP tools

DESTRUCTIVE 3 tools

Destructive clear_app_data Clear application data for a package Destructive delete_contact Delete a contact or all contacts Destructive delete_file Delete a file or directory

EXECUTE 15 tools

Execute call_phone Make a phone call (SIM card 1 only) Execute end_call End the current phone call Execute execute_adb_shell_command Executes an ADB command and returns the output or an error. Execute execute_script execute_script Execute exit_service Exit the AutoBot service Execute play_music Play music from a URL Execute start_screen_recording Start screen recording Execute stop_all_scripts Stop all running AutoX.js scripts Execute stop_app Stop an application by package name Execute stop_music Stop playing music Execute stop_screen_recording Stop screen recording Execute turn_safe_mode_off Turn off safe mode Execute turn_safe_mode_on Turn on safe mode Execute turn_screen_off Turn off the screen (device remains active for control/casting) Execute turn_screen_on Turn on the screen

WRITE 7 tools

Write disable_screen_keep_alive 禁用屏幕保持常亮功能 Write enable_screen_keep_alive 启用屏幕保持常亮功能 Write insert_contact Insert a new contact Write send_sms Send an SMS message Write set_clipboard_text Set clipboard text Write set_device_name Set a display name for the device Write set_screen_timeout 设置屏幕超时时间

READ 19 tools

Read get_clipboard_text Get clipboard text Read get_contacts Get all contacts or a specific contact by phone number Read get_device_id Get the device ID Read get_device_info Get detailed information about the device Read get_device_ip Get all IP addresses of the device Read get_device_name Get the display name of the device Read get_file_url Get the download URL for a file Read get_package_action_intents Get all non-data actions from Activity Resolver Table for a package Read get_packages Get all installed packages on the device Read get_screen_info Get information about the screen (dimensions, rotation) Read get_screen_rotation Get the screen rotation Read get_screen_timeout 获取当前屏幕超时设置 Read get_sms Get all SMS messages or messages from a specific number Read get_top_activity Get information about the current top activity Read get_uilayout get_uilayout Read get_version Get the AutoBot version number Read hello Test connection to AutoBot server Read is_safe_mode Check if safe mode is enabled Read list_files List files in a directory

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about AutoBot MCP

Can an AI agent delete data through the AutoBot MCP server? +

Yes. The AutoBot MCP server exposes 3 destructive tools including clear_app_data, delete_contact, delete_file. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through AutoBot MCP? +

The AutoBot MCP server has 7 write tools including disable_screen_keep_alive, enable_screen_keep_alive, insert_contact. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach AutoBot MCP.

How many tools does the AutoBot MCP server expose? +

44 tools across 4 categories: Destructive, Execute, Read, Write. 19 are read-only. 25 can modify, create, or delete data.

How do I enforce a policy on AutoBot MCP? +

Register the AutoBot MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every AutoBot MCP tool call.

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

ENFORCE POLICY ON AUTOBOT →

Instant setup, no code required.

44 AutoBot MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.