adb_end_call · Openclaw Adb MCP: Risk & Policy

WHAT IT DOES

What adb_end_call does on Openclaw Adb

AI agents invoke adb_end_call 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_end_call needs a policy

This tool executes an action on an external device (ending a phone call) via ADB. It is not a simple read or write operation; it triggers a real-world telephony event. While it doesn't delete data or move money, it interrupts an active communication session, which could be disruptive if misused. Classified as Execute with medium severity due to the limited but real-world impact of terminating calls.

From the tool's definition 'End the current phone call' — triggers an external telephony operation on a connected Android device via ADB

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_end_call Rate-limited

adb_end_call 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_end_call": {
      "limits": [
        {
          "counter": "adb_end_call_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_end_call

What does the adb_end_call tool do? +

End the current phone 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_end_call? +

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

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

Can I rate-limit adb_end_call? +

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

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

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