android_send_key_event · Android MCP Server MCP

WHAT IT DOES

What android_send_key_event does on Android MCP Server

AI agents invoke android_send_key_event to trigger actions in Android MCP Server. 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 android_send_key_event needs a policy

This tool triggers external operations on a physical/virtual Android device by sending key events via ADB. It simulates hardware key presses that can navigate the UI, confirm actions, or trigger system behaviors. This falls under Execute as it performs device-side actions whose effects depend on the current device state and which key is sent.

From the tool's definition Send a key event to the Android device (e.g., KEYEVENT_HOME, KEYEVENT_BACK, KEYEVENT_ENTER)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_send_key_event Rate-limited

android_send_key_event 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": {
    "android_send_key_event": {
      "limits": [
        {
          "counter": "android_send_key_event_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 Android MCP Server, so you can run agents against it safely.

FAQ

Questions about android_send_key_event

What does the android_send_key_event tool do? +

Send a key event to the Android device (e.g., KEYEVENT_HOME, KEYEVENT_BACK, KEYEVENT_ENTER). It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_send_key_event? +

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

What risk level is android_send_key_event? +

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

Can I rate-limit android_send_key_event? +

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

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

android_send_key_event is provided by the Android MCP Server MCP server (jduartedj/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.