check_adb_status

Check if ADB is installed and accessible

SERVERAndroid Forensics ADB MCP Server SOURCE0x-professor/droidforensics-suite

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0x-professor-droidforensics-suite/check-adb-status.md

WHAT IT DOES

What check_adb_status does on Android Forensics ADB MCP Server

AI agents call check_adb_status to retrieve information from Android Forensics ADB MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_adb_status is rated Low

This tool merely queries the system to verify ADB availability. It retrieves information about the ADB tool's presence and accessibility without performing any side effects, data acquisition, command execution, or changes to device state. This is a straightforward read operation analogous to a 'get' or 'status' query.

From the tool's definition Tool description states 'Check if ADB is installed and accessible' — a pure status check with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_adb_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Android Forensics ADB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_adb_status, this is the rule to start with:

check_adb_status Allowed

check_adb_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_adb_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Android Forensics ADB MCP Server, apply this rule, and every check_adb_status call is checked against it from then on.

FAQ

Questions about check_adb_status

What does the check_adb_status tool do? +

Check if ADB is installed and accessible. It is categorised as a Read tool in the Android Forensics ADB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_adb_status? +

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

What risk level is check_adb_status? +

check_adb_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_adb_status? +

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

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

check_adb_status is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Android Forensics ADB MCP Server, and thousands of servers like it.

This server

All 58 Android Forensics ADB MCP Server tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →