adb_network_connections
Show active network connections on the device (TCP/UDP). Similar to netstat — shows established connections, listening ports, and connection states.
This record as markdown: /tools/io-github-fullread-deepadb/adb-network-connections.md
What adb_network_connections does on Deepadb
AI agents call adb_network_connections 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_network_connections is rated Low
This tool performs read-only querying of network connection state. It retrieves data about TCP/UDP connections, established connections, listening ports, and connection states. There are no side effects, no code execution, no data modification, and no destructive operations.
From the tool's definition Tool description explicitly states it 'Show[s] active network connections' and is 'Similar to netstat' — both are introspection/query operations that retrieve information about running connections without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs adb_network_connections 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_network_connections, this is the rule to start with:
adb_network_connections 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_network_connections call is checked against it from then on.
Questions about adb_network_connections
Show active network connections on the device (TCP/UDP). Similar to netstat — shows established connections, listening ports, and connection states. 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_network_connections: 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_network_connections 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_network_connections 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_network_connections. 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_network_connections 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