adb_keyevent

Send a key event (e.g. 4 = BACK).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/adb-keyevent.md

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.

RISK

Why adb_keyevent is rated High

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

The rule that runs adb_keyevent safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_keyevent, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_keyevent call is checked against it from then on.

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.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →