adb_keyevent · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What adb_keyevent does on LocalAnt

AI agents invoke adb_keyevent to trigger actions in LocalAnt. 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_keyevent needs a policy

Sending key events to a device is an external operation that simulates user input (navigation, media controls, power, etc.). It doesn't read data, write files, or delete anything permanently, but it executes device-level actions whose effects depend on arguments (e.g., HOME, BACK, POWER, VOLUME). Misuse could trigger unintended navigation or app actions on the connected device.

From the tool's definition "Send a key event (e.g. 4 = BACK)" — triggers an input/control action on a connected Android device via ADB

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adb_keyevent Rate-limited

adb_keyevent 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_keyevent": {
      "limits": [
        {
          "counter": "adb_keyevent_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 LocalAnt, so you can run agents against it safely.

FAQ

Questions about adb_keyevent

What does the adb_keyevent tool do? +

Send a key event (e.g. 4 = BACK). It is categorised as a Execute tool in the LocalAnt 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_keyevent? +

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

What risk level is adb_keyevent? +

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

Can I rate-limit adb_keyevent? +

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

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

adb_keyevent is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.