adb_baseband_info

Get comprehensive modem/baseband identification: firmware version, RIL implementation, chipset, IMEI, SIM state, and radio capabilities.

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-baseband-info.md

WHAT IT DOES

What adb_baseband_info does on Deepadb

AI agents call adb_baseband_info 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_baseband_info is rated Low

This is a read operation that queries device telephony and hardware information. While categorized as Read (retrieves/queries data with no side effects), the severity is elevated to high because it exposes sensitive identifying information (IMEI, SIM state, firmware versions) that could be used for device fingerprinting, SIM swapping attacks, or targeted exploitation if an AI agent abuses access to leak this data.

From the tool's definition Tool retrieves modem/baseband identification data including firmware version, RIL implementation, chipset, IMEI, SIM state, and radio capabilities. No modification or execution described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_baseband_info 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_baseband_info, this is the rule to start with:

adb_baseband_info Allowed

adb_baseband_info 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_baseband_info": {}
  }
}

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_baseband_info call is checked against it from then on.

FAQ

Questions about adb_baseband_info

What does the adb_baseband_info tool do? +

Get comprehensive modem/baseband identification: firmware version, RIL implementation, chipset, IMEI, SIM state, and radio capabilities. 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_baseband_info? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_baseband_info: 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_baseband_info? +

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

Can I rate-limit adb_baseband_info? +

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

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

adb_baseband_info 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

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

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