adb_setup_status · Termux MCP Server MCP: Risk & Policy

WHAT IT DOES

What adb_setup_status does on Termux MCP Server

AI agents use adb_setup_status to create or update resources in Termux MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Termux MCP Server environment.

WHY IT NEEDS A POLICY

Why adb_setup_status needs a policy

An AI agent can call adb_setup_status faster than any human can review — one bad instruction and it creates or modifies resources in Termux MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_setup_status Rate-limited

adb_setup_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_setup_status": {
      "limits": [
        {
          "counter": "adb_setup_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about adb_setup_status

What does the adb_setup_status tool do? +

Check if ADB is set up and connected. On Android 12+, ADB is required. It is categorised as a Write tool in the Termux MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on adb_setup_status? +

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

What risk level is adb_setup_status? +

adb_setup_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit adb_setup_status? +

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

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

adb_setup_status is provided by the Termux MCP Server MCP server (xlisp/termux-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.