adb_root_status

Checks if the Android device is rooted and provides detailed root status.

SERVERRenef SOURCEahmeth4n/renef-mcp

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/ahmeth4n-renef-mcp/adb-root-status.md

WHAT IT DOES

What adb_root_status does on Renef

AI agents call adb_root_status to retrieve information from Renef without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why adb_root_status is rated Low

This tool performs a read-only status check on the Android device. It queries whether the device is rooted and returns status information. There are no side effects, code execution, data modification, or irreversible actions. While the broader server provides dangerous instrumentation capabilities (native hooking, memory manipulation), this specific tool is a simple information retrieval operation.

From the tool's definition Tool name 'adb_root_status' and description 'Checks if the Android device is rooted and provides detailed root status' indicate a query operation that retrieves device state information without modification or execution.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_root_status safely

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

adb_root_status Allowed

adb_root_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": {
    "adb_root_status": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Renef, apply this rule, and every adb_root_status call is checked against it from then on.

FAQ

Questions about adb_root_status

What does the adb_root_status tool do? +

Checks if the Android device is rooted and provides detailed root status. It is categorised as a Read tool in the Renef MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_root_status? +

Register the Renef MCP server in PolicyLayer and add a rule for adb_root_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 Renef. Nothing to install.

What risk level is adb_root_status? +

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

Can I rate-limit adb_root_status? +

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

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

adb_root_status is provided by the Renef MCP server (ahmeth4n/renef-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Renef, and thousands of servers like it.

This server

All 75 Renef 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 →