adb_telephony
Get telephony state including cell info, signal strength, and network registration.
This record as markdown: /tools/io-github-fullread-deepadb/adb-telephony.md
What adb_telephony does on Deepadb
AI agents call adb_telephony 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.
Why adb_telephony is rated Low
This tool retrieves telephony metadata from the device without modifying, executing, or destructively acting upon it. The read-only nature and informational scope (network state inspection) place it firmly in the Read category. Severity is low because leaked telephony state data has limited immediate impact compared to functional capabilities.
From the tool's definition Tool description explicitly states 'Get telephony state' — retrieval only. Actions listed are 'cell info, signal strength, and network registration' — all queries with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs adb_telephony 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_telephony, this is the rule to start with:
adb_telephony is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_telephony call is checked against it from then on.
Questions about adb_telephony
Get telephony state including cell info, signal strength, and network registration. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_telephony: 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.
adb_telephony is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the adb_telephony 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.
Set action: deny in the PolicyLayer policy for adb_telephony. 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.
adb_telephony 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.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue