android_key

Send a key event to the Android device. Use keycode (e.g., '3' for HOME, '4' for BACK) or common name (e.g., 'HOME').

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

High RISK CLASS

Category Execute

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/android-key.md

WHAT IT DOES

What android_key does on Dialogbrain

AI agents invoke android_key to trigger actions in Dialogbrain. 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.

Parameter	Type	Required	Description
`code`	string	Yes	Key code: numeric (e.g., '3', '4') or common name (HOME, BACK, POWER, VOLUME_UP, VOLUME_DOWN, MENU, SEARCH, ENTER, DEL)
`channel_account_id`	integer	—	Android device channel_account ID. Omit when the workspace has a single Android device; REQUIRED when it has more than one (e.g. WhatsApp + LINE), else the call

Parameters from the server's own tool schema.

RISK

Why android_key is rated High

This tool executes key events on an Android device, which constitutes running an external operation whose effects depend on the arguments provided. While not directly destructive or financial, sending key events can trigger arbitrary UI interactions (e.g., HOME, BACK, or other keycodes), potentially causing unintended navigation or app actions on the device.

From the tool's definition 'Send a key event to the Android device' — triggers an external operation on a physical/virtual device

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs android_key safely

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

android_key Rate-limited

android_key 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_key": {
      "limits": [
        {
          "counter": "android_key_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 Dialogbrain, apply this rule, and every android_key call is checked against it from then on.

FAQ

Questions about android_key

What does the android_key tool do? +

Send a key event to the Android device. Use keycode (e.g., '3' for HOME, '4' for BACK) or common name (e.g., 'HOME'). It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does android_key accept? +

android_key accepts 2 parameters: code, channel_account_id. Required: code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on android_key? +

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

What risk level is android_key? +

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

Can I rate-limit android_key? +

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

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

android_key is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 232 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

qt_key_press on Qt →send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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