Relay a single input event to the Android device via adb: tap (x,y), text (types a string), key (keyevent keycode, e.g. 66=ENTER/67=DEL/4=BACK), or swipe (x1,y1→x2,y2 over dur ms). Lets automation drive the device, or a human-built UI forward taps/keystrokes.
AI agents call droid_input to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
x | integer | — | tap X |
y | integer | — | tap Y |
x1 | integer | — | swipe start X |
x2 | integer | — | swipe end X |
y1 | integer | — | swipe start Y |
y2 | integer | — | swipe end Y |
dur | integer | — | swipe duration ms (default 300) |
text | string | — | text to type (spaces handled) |
type | string | Yes | |
device | string | — | adb serial (default: first attached device) |
keycode | integer | — | Android keyevent code |
Parameters from the server's own tool schema.
Even though droid_input only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Relay a single input event to the Android device via adb: tap (x,y), text (types a string), key (keyevent keycode, e.g. 66=ENTER/67=DEL/4=BACK), or swipe (x1,y1→x2,y2 over dur ms). Lets automation drive the device, or a human-built UI forward taps/keystrokes. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
droid_input accepts 11 parameters: x, y, x1, x2, y1, y2, dur, text, type, device, keycode. Required: type. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for droid_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 Yaver. Nothing to install.
droid_input is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the droid_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 droid_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.
droid_input is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.