adb_reverse
Reverse-forward a device port to a port on the host (device → host). Use for letting device apps reach services on your machine.
This record as markdown: /tools/io-github-fullread-deepadb/adb-reverse.md
What adb_reverse does on Deepadb
AI agents invoke adb_reverse 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_reverse is rated High
This tool sets up a network tunnel/port forwarding from the Android device to the host machine. It triggers an external operation (ADB reverse port forwarding) that modifies network connectivity between the device and host. It is not a simple read, but also not destructive or financial. It falls under Execute as it configures active network routing that could expose host services to the device.
From the tool's definition Reverse-forward a device port to a port on the host (device → host). Use for letting device apps reach services on your machine.
Attacks that exploit this kind of access
The rule that runs adb_reverse 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_reverse, this is the rule to start with:
adb_reverse stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_reverse call is checked against it from then on.
Questions about adb_reverse
Reverse-forward a device port to a port on the host (device → host). Use for letting device apps reach services on your machine. 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.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_reverse: 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_reverse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_reverse 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_reverse. 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_reverse 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.
Across the catalogue