adb_termux_exec · ADB MCP Server MCP: Risk & Policy

WHAT IT DOES

What adb_termux_exec does on ADB MCP Server

AI agents invoke adb_termux_exec to trigger actions in ADB MCP Server. 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 IT NEEDS A POLICY

Why adb_termux_exec needs a policy

This tool executes arbitrary bash commands on an Android device via Termux, giving it the ability to run any command with the privileges of the Termux user. This is a classic Execute pattern with critical severity because: (1) it can trigger external operations with unpredictable effects depending on the command argument, (2) it could be leveraged to install malware, exfiltrate data, or compromise the device, (3)…

From the tool's definition Tool description states it 'Execute[s] a command in Termux bash', and the server description confirms it supports 'shell execution'. The ⚠️ warning requiring 'confirm=true' further indicates this tool performs potentially dangerous operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_termux_exec Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_termux_exec": {
      "limits": [
        {
          "counter": "adb_termux_exec_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about adb_termux_exec

What does the adb_termux_exec tool do? +

Execute a command in Termux bash. ⚠️ Requires confirm=true. It is categorised as a Execute tool in the ADB MCP Server 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_termux_exec? +

Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_termux_exec: 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 ADB MCP Server. Nothing to install.

What risk level is adb_termux_exec? +

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

Can I rate-limit adb_termux_exec? +

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

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

adb_termux_exec is provided by the ADB MCP Server MCP server (lll-404/adb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.