Simulate user input interactions (tap, text, swipe, keyevents) or click by UI element.
AI agents invoke inject-input to trigger actions in Android Mcp Toolkit. 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.
This tool executes input events on an Android device, simulating physical user interactions. It triggers external operations (touch/key events via ADB input commands) whose effects depend on arguments - e.g., tapping UI elements, entering text, or pressing keys. These actions can cause arbitrary app-level effects (submitting forms, navigating, triggering purchases) making misuse potentially high-impact.
From the tool's definition Simulate user input interactions (tap, text, swipe, keyevents) or click by UI element
Documented attack patterns abuse exactly the kind of access inject-input gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Mcp Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for inject-input:
{
"version": "1",
"default": "deny",
"tools": {
"inject-input": {
"limits": [
{
"counter": "inject-input_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} inject-input 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.
Free to start. No card required.
Simulate user input interactions (tap, text, swipe, keyevents) or click by UI element. It is categorised as a Execute tool in the Android Mcp Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Mcp Toolkit MCP server in PolicyLayer and add a rule for inject-input: 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 Toolkit. Nothing to install.
inject-input is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the inject-input 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.
Set action: deny in the PolicyLayer policy for inject-input. 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.
inject-input is provided by the Android Mcp Toolkit MCP server (nam0101/android-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Mcp Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Android Mcp Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.