adb_force_stop · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_force_stop does on Openclaw Adb

AI agents invoke adb_force_stop to trigger actions in Openclaw Adb. 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_force_stop needs a policy

Force-stopping an application is an external execution action that immediately kills a running process on a connected Android device. While the app can be restarted (not permanently destructive), the action has significant blast radius: it can interrupt active operations, lose unsaved data, disrupt foreground services, and affect device functionality.

From the tool's definition 'Force stop an application' — terminates a running application process on the Android device via ADB

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_force_stop Rate-limited

adb_force_stop 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_force_stop": {
      "limits": [
        {
          "counter": "adb_force_stop_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 Openclaw Adb, so you can run agents against it safely.

FAQ

Questions about adb_force_stop

What does the adb_force_stop tool do? +

Force stop an application. It is categorised as a Execute tool in the Openclaw Adb 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_force_stop? +

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

What risk level is adb_force_stop? +

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

Can I rate-limit adb_force_stop? +

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

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

adb_force_stop is provided by the Openclaw Adb MCP server (wilsonbeam/openclaw-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.