input_text · Maa MCP: Risk & Policy

WHAT IT DOES

What input_text does on MaaMCP

AI agents invoke input_text to trigger actions in MaaMCP. 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 input_text needs a policy

Given the server context of Android/Windows automation and sibling tools like 'click', 'click_key', 'connect_adb_device', and 'connect_window', 'input_text' almost certainly sends keystrokes or text input to a device or window, triggering external operations on a controlled system. This constitutes an Execute-level action.

From the tool's definition Tool name 'input_text' on a server providing Android device and Windows desktop automation capabilities (MaaFramework-based MCP server)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

input_text Rate-limited

input_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "input_text": {
      "limits": [
        {
          "counter": "input_text_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 MaaMCP, so you can run agents against it safely.

FAQ

Questions about input_text

What does the input_text tool do? +

input_text. It is categorised as a Execute tool in the MaaMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on input_text? +

Register the Maa MCP server in PolicyLayer and add a rule for input_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 MaaMCP. Nothing to install.

What risk level is input_text? +

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

Can I rate-limit input_text? +

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

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

input_text is provided by the Maa MCP server (maa-ai/maamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.