adb_dial_number · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_dial_number does on Openclaw Adb

AI agents invoke adb_dial_number 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_dial_number needs a policy

This tool triggers an external operation on the Android device by opening the dialer app with a pre-filled number. While it does not complete the call itself, it executes a device action (launching an intent/activity). Since the user must still press call, the blast radius is low — it cannot autonomously place calls or incur charges, but it does interact with device functions.

From the tool's definition Open the dialer with a number (does not dial - user must press call)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_dial_number Rate-limited

adb_dial_number 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_dial_number": {
      "limits": [
        {
          "counter": "adb_dial_number_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_dial_number

What does the adb_dial_number tool do? +

Open the dialer with a number (does not dial - user must press call). 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_dial_number? +

Register the Openclaw Adb MCP server in PolicyLayer and add a rule for adb_dial_number: 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_dial_number? +

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

Can I rate-limit adb_dial_number? +

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

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

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