This record as markdown: /tools/1shin-7-ya-frida-mcp/adb-disconnect.md
What adb_disconnect does on Ya Frida
AI agents invoke adb_disconnect to trigger actions in Ya Frida. 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_disconnect is rated High
This tool terminates a TCP/IP connection to a device, which is an external operation with side effects (dropping an active connection). It is not purely read-only, nor is it irreversibly destructive to data, but it triggers an external operational change. Misuse could disrupt ongoing ADB sessions or instrumentation operations.
From the tool's definition Disconnect a TCP/IP device
Attacks that exploit this kind of access
The rule that runs adb_disconnect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ya Frida, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_disconnect, this is the rule to start with:
adb_disconnect 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 Ya Frida, apply this rule, and every adb_disconnect call is checked against it from then on.
Questions about adb_disconnect
Disconnect a TCP/IP device. It is categorised as a Execute tool in the Ya Frida MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ya Frida MCP server in PolicyLayer and add a rule for adb_disconnect: 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 Ya Frida. Nothing to install.
adb_disconnect 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_disconnect 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_disconnect. 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_disconnect is provided by the Ya Frida MCP server (1shin-7/ya-frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ya Frida, and thousands of servers like it.
Across the catalogue