# ClearInput

ClearInput action, the position of the placeholder or text content in the target input field. If there is no content, locate the center of the input field.. Parameters: locate? (object) - The input field to be cleared

Agent View of the PolicyLayer registry record for `ClearInput`. HTML page: https://policylayer.com/tools/android/clearinput

## Facts

- Tool: `ClearInput`
- Server: Android (`@midscene/android-mcp`) — https://policylayer.com/tools/android.md
- Install: `npx -y @midscene/android-mcp`
- Homepage: https://www.npmjs.com/package/@midscene/android-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 7
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `locate` | object | no | The input field to be cleared |
| `android.deviceId` | string | no | Android device ID (from adb devices) |
| `android.useScrcpy` | boolean | no | Enable scrcpy accelerated screenshots |
| `android.aiActContext` | string | no | Background knowledge passed to aiAct. Default: no extra context. |
| `android.waitAfterAction` | number | no | Wait time in milliseconds after each action execution. Default: 300ms. |
| `android.replanningCycleLimit` | integer | no | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
| `android.screenshotShrinkFactor` | number | no | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ClearInput",
    "arguments": {}
  }
}
```

## Why ClearInput is rated Critical

ClearInput irreversibly erases the content of an input field on an Android device. While the data loss is scoped to a single UI field, the action cannot be undone programmatically once the content is cleared, making it Destructive rather than Write. Misuse could cause loss of unsaved user data in forms or text fields.

From the tool's own definition: "ClearInput action...the input field to be cleared"

Risk signals: High parameter count (12 properties)

## Use case

AI agents call ClearInput to permanently remove resources in Android, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Android:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ClearInput"
  ]
}
```

## Other tools on Android (22)

- `act` — Execute — https://policylayer.com/tools/android/act.md
- `android_connect` — Execute — https://policylayer.com/tools/android/android-connect.md
- `AndroidBackButton` — Execute — https://policylayer.com/tools/android/androidbackbutton.md
- `AndroidHomeButton` — Execute — https://policylayer.com/tools/android/androidhomebutton.md
- `AndroidRecentAppsButton` — Execute — https://policylayer.com/tools/android/androidrecentappsbutton.md
- `CursorMove` — Execute — https://policylayer.com/tools/android/cursormove.md
- `DoubleClick` — Execute — https://policylayer.com/tools/android/doubleclick.md
- `DragAndDrop` — Execute — https://policylayer.com/tools/android/draganddrop.md
- `KeyboardPress` — Execute — https://policylayer.com/tools/android/keyboardpress.md
- `Launch` — Execute — https://policylayer.com/tools/android/launch.md
- `LongPress` — Execute — https://policylayer.com/tools/android/longpress.md
- `Pinch` — Execute — https://policylayer.com/tools/android/pinch.md
- `PullGesture` — Execute — https://policylayer.com/tools/android/pullgesture.md
- `RunAdbShell` — Execute — https://policylayer.com/tools/android/runadbshell.md
- `Scroll` — Execute — https://policylayer.com/tools/android/scroll.md
- `Swipe` — Execute — https://policylayer.com/tools/android/swipe.md
- `Tap` — Execute — https://policylayer.com/tools/android/tap.md
- `Terminate` — Execute — https://policylayer.com/tools/android/terminate.md
- `take_screenshot` — Read — https://policylayer.com/tools/android/take-screenshot.md
- `android_disconnect` — Write — https://policylayer.com/tools/android/android-disconnect.md
- `assert` — Write — https://policylayer.com/tools/android/assert.md
- `Input` — Write — https://policylayer.com/tools/android/input.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=android · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/android