High Risk →

send_text

Send text input to the currently focused UI element. Can optionally clear existing text before sending. Perfect for form filling, search boxes, and text fields.

How to control send_text ↓

AI agents invoke send_text to trigger actions in MCP Android Agent. 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 performs an action on an Android device by injecting text input into the currently focused UI element. It goes beyond simply writing data — it executes an interaction with a live device's UI, which can have unpredictable side effects depending on what element is focused (e.g., submitting forms, triggering searches, entering credentials).

From the tool's definition 'Send text input to the currently focused UI element. Can optionally clear existing text before sending.' - triggers external UI operations on a device

Documented attack patterns abuse exactly the kind of access send_text gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for send_text:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_text": {
      "limits": [
        {
          "counter": "send_text_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send_text 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 Android Agent — 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_text tool do? +

Send text input to the currently focused UI element. Can optionally clear existing text before sending. Perfect for form filling, search boxes, and text fields. It is categorised as a Execute tool in the MCP Android Agent 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_text? +

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

What risk level is send_text? +

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

Can I rate-limit send_text? +

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

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

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

Enforce policy on every MCP Android Agent tool call.

Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

28 MCP Android Agent 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.