Android Forensics ADB MCP Server

58 tools. 12 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

12 can modify or destroy data
46 read-only
58 tools total

Community server · catalogue entry verified 12/06/2026

How to control Android Forensics ADB MCP Server ↓

What Android Forensics ADB MCP Server exposes to your agents

Read (46) Write / Execute (10) Destructive / Financial (1)
Critical Risk

The most dangerous Android Forensics ADB MCP Server tools

12 of Android Forensics ADB MCP Server's 58 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Android Forensics ADB MCP Server

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

Deny destructive operations
{
  "create_full_backup": {
    "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
{
  "combine_reports": {
    "limits": [
      {
        "counter": "combine_reports_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "parse_browser_history": {
    "limits": [
      {
        "counter": "parse_browser_history_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Android Forensics ADB MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON ANDROID FORENSICS ADB →

Free to start. No card required.

All 58 Android Forensics ADB MCP Server tools

READ 46 tools
Read parse_browser_history parse_browser_history Read parse_call_log_db Parse Android call log database (calllog.db or contacts2.db). Read parse_contacts_db Parse Android contacts database (contacts2.db). Read parse_generic_sqlite parse_generic_sqlite Read parse_sms_db Parse Android SMS/MMS database (mmssms.db). Read adb_devices List all connected Android devices via ADB Read adb_pull_data Pull files or directories from the device to local storage. Read analyze_facebook_messenger Analyze Facebook Messenger database (threads_db2). Read analyze_gmail Analyze Gmail database (mailstore..db). Read analyze_instagram Analyze Instagram database. Read analyze_network_connections Analyze active network connections and configuration. Read analyze_partition_info Analyze device partitions and mount points. Read analyze_telegram Analyze Telegram database. Read analyze_whatsapp analyze_whatsapp Read capture_dmesg Capture kernel ring buffer (dmesg). Read capture_logcat capture_logcat Read check_adb_status Check if ADB is installed and accessible Read check_root_status Comprehensive root/jailbreak detection. Read collect_common_artifacts collect_common_artifacts Read collect_forensic_artifacts Collect common forensic artifacts from Android device. Read dump_database dump_database Read dump_system_settings Dump all system settings (secure, system, global). Read extract_app_credentials extract_app_credentials Read extract_backup_to_tar Extract Android Backup (.ab) file to TAR format. Read extract_exif_metadata Extract EXIF metadata from image files. Read extract_media_gallery_metadata extract_media_gallery_metadata Read get_account_info Get registered accounts on the device. Read get_comprehensive_device_info Get comprehensive device information for forensic documentation. Read get_device_accounts Get list of accounts configured on the device. Read get_device_identifiers Get all device identifiers for forensic tracking (IMEI, serial, etc.). Read get_device_info Get comprehensive device information for forensic documentation Read get_device_security_status Get device security configuration and status. Read get_device_users Get list of user profiles on the device (Android multi-user). Read get_installed_packages Get list of all installed packages with details. Read get_running_processes Get list of running processes. Read list_connected_devices List all Android devices connected via USB or wireless ADB. Read list_installed_apps_data List all installed applications and their data directories. Read list_installed_packages List all installed packages on the device Read list_remote_directory List contents of a directory on the device. Read pull_directory Pull an entire directory from the device recursively. Read pull_file Pull a specific file from the device. Read pull_sdcard Pull entire SD card / internal storage content. Read take_device_screenshot Capture current screen of the device. Read create_timeline Create a unified timeline from multiple artifact sources. Read generate_executive_summary Generate an executive summary for non-technical stakeholders. Read generate_timeline_report Generate a chronological timeline report of events.

Related servers

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

Questions about Android Forensics ADB MCP Server

Can an AI agent delete data through the Android Forensics ADB MCP Server MCP server? +

Yes. The Android Forensics ADB MCP Server server exposes 1 destructive tools including create_full_backup. 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 Android Forensics ADB MCP Server? +

The Android Forensics ADB MCP Server server has 4 write tools including combine_reports, create_package_backup, generate_evidence_manifest. 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 Android Forensics ADB MCP Server.

How many tools does the Android Forensics ADB MCP Server MCP server expose? +

58 tools across 3 categories: Execute, Read, Write. 46 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on Android Forensics ADB MCP Server? +

Register the Android Forensics ADB MCP Server 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 Android Forensics ADB MCP Server tool call.

Deterministic rules across all 58 Android Forensics ADB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

58 Android Forensics ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.