adb_tunnel_open

Open a managed tunnel between host and device. Higher-level convenience wrapper over adb_forward / adb_reverse: auto-picks a free host port when one isn

SERVERDeepadb SOURCEdeepadb
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-tunnel-open.md

What adb_tunnel_open does on Deepadb

AI agents invoke adb_tunnel_open to trigger actions in Deepadb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why adb_tunnel_open is rated High

This tool establishes a network tunnel between the host and an Android device via ADB port forwarding/reversing. It triggers an external operation (network port binding and forwarding) with real side effects — opening ports and creating network connectivity. This fits Execute since it initiates an ongoing network operation.

From the tool's definition "Open a managed tunnel between host and device" and "convenience wrapper over adb_forward / adb_reverse: auto-picks a free host port"

Questions about adb_tunnel_open

What does the adb_tunnel_open tool do? +

Open a managed tunnel between host and device. Higher-level convenience wrapper over adb_forward / adb_reverse: auto-picks a free host port when one isn. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adb_tunnel_open? +

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

adb_tunnel_open is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adb_tunnel_open? +

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

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

adb_tunnel_open 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Deepadb's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.