adb_at_detect

Auto-detect the modem AT command device node. Identifies the chipset family (Shannon, Qualcomm, MediaTek, Unisoc) and probes known device node paths. Requires root. Returns the first responding node.

SERVERDeepadb SOURCEdeepadb

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/io-github-fullread-deepadb/adb-at-detect.md

WHAT IT DOES

What adb_at_detect does on Deepadb

AI agents call adb_at_detect to retrieve information from Deepadb 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_at_detect is rated Low

The tool probes and identifies hardware device nodes without modifying or executing commands through them. It is a discovery/detection operation. Severity is medium because it requires root access and exposes sensitive modem/chipset topology information that could aid further exploitation.

From the tool's definition Auto-detect the modem AT command device node. Identifies the chipset family... and probes known device node paths. Returns the first responding node.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_at_detect safely

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

adb_at_detect Allowed

adb_at_detect 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_at_detect": {}
  }
}

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

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

FAQ

Questions about adb_at_detect

What does the adb_at_detect tool do? +

Auto-detect the modem AT command device node. Identifies the chipset family (Shannon, Qualcomm, MediaTek, Unisoc) and probes known device node paths. Requires root. Returns the first responding node. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_at_detect? +

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

What risk level is adb_at_detect? +

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

Can I rate-limit adb_at_detect? +

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

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

adb_at_detect is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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