High Risk →

send-keys-to-device

Send keys directly to the device without focusing on any element

How to control send-keys-to-device ↓

AI agents invoke send-keys-to-device to trigger actions in MCP Appium 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.

High Risk

This tool sends keyboard input directly to a mobile device, triggering external operations (key events/input) on the device. It can simulate button presses or text input at the OS level without element focus, which constitutes executing an action on an external system. Misuse could trigger unintended navigation, commands, or system interactions.

From the tool's definition Send keys directly to the device without focusing on any element

Documented attack patterns abuse exactly the kind of access send-keys-to-device gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Appium Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send-keys-to-device:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send-keys-to-device": {
      "limits": [
        {
          "counter": "send-keys-to-device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send-keys-to-device 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.

  1. Create a free account and register MCP Appium Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the send-keys-to-device tool do? +

Send keys directly to the device without focusing on any element. It is categorised as a Execute tool in the MCP Appium 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 send-keys-to-device? +

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

What risk level is send-keys-to-device? +

send-keys-to-device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send-keys-to-device? +

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

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

send-keys-to-device is provided by the MCP Appium Server MCP server (rahulec08/appium-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Appium Server tool call.

Deterministic rules across all 110 MCP Appium Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

110 MCP Appium Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.