Scroll
Scroll action, Scroll the page or a scrollable element to browse content. This is the preferred way to scroll on all platforms, including mobile. Supports scrollToBottom/scrollToTop for boundary navigation. Default: direction down, scrollType singleAction, distance null.. Parameters: scrollType? ...
This record as markdown: /tools/android/scroll.md
What Scroll does on Android
AI agents invoke Scroll to trigger actions in Android. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
locate | object | — | Describe the target element to be scrolled on, like "the table" or "the list" or "the content area" or "the scrollable area". Do NOT provide a general intent li |
distance | number | null | — | The distance in pixels to scroll |
direction | string | — | The direction to scroll. Only effective when scrollType is "singleAction". |
scrollType | string | — | The scroll behavior: "singleAction" for a single scroll action, "scrollToBottom" for scrolling all the way to the bottom by rapidly scrolling 5-10 times (skippi |
android.deviceId | string | — | Android device ID (from adb devices) |
android.useScrcpy | boolean | — | Enable scrcpy accelerated screenshots |
android.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
android.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
android.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
android.screenshotShrinkFactor | number | — | 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.
Why Scroll is rated High
This tool triggers a physical UI interaction on an Android device (scrolling), which is an external operation that depends on arguments. It falls under Execute as it performs browser/device actions rather than simply reading or writing data. Misuse could cause unintended navigation but blast radius is moderate.
From the tool's definition Scroll action, Scroll the page or a scrollable element to browse content... Supports scrollToBottom/scrollToTop for boundary navigation...
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs Scroll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Android, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Scroll, this is the rule to start with:
Scroll 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Android, apply this rule, and every Scroll call is checked against it from then on.
Questions about Scroll
Scroll action, Scroll the page or a scrollable element to browse content. This is the preferred way to scroll on all platforms, including mobile. Supports scrollToBottom/scrollToTop for boundary navigation. Default: direction down, scrollType singleAction, distance null.. Parameters: scrollType? (enum('singleAction', 'scrollToBottom', 'scrollToTop', 'scrollToRight', 'scrollToLeft')) - The scroll behavior: "singleAction" for a single scroll action, "scrollToBottom" for scrolling all the way to the bottom by rapidly scrolling 5-10 times (skipping intermediate content until reaching the bottom), "scrollToTop" for scrolling all the way to the top by rapidly scrolling 5-10 times (skipping intermediate content until reaching the top), "scrollToRight" for scrolling all the way to the right by rapidly scrolling multiple times, "scrollToLeft" for scrolling all the way to the left by rapidly scrolling multiple times; direction? (enum('down', 'up', 'right', 'left')) - The direction to scroll. Only effective when scrollType is "singleAction".; distance? (number) - The distance in pixels to scroll; locate? (object) - Describe the target element to be scrolled on, like "the table" or "the list" or "the content area" or "the scrollable area". Do NOT provide a general intent like "scroll to find some element". It is categorised as a Execute tool in the Android MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Scroll accepts 10 parameters: locate, distance, direction, scrollType, android.deviceId, android.useScrcpy, android.aiActContext, android.waitAfterAction, android.replanningCycleLimit, android.screenshotShrinkFactor. The full parameter table on this page comes from the server's own tool schema.
Register the Android MCP server in PolicyLayer and add a rule for Scroll: 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. Nothing to install.
Scroll 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 Scroll 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 Scroll. 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.
Scroll is provided by the Android MCP server (@midscene/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Android, and thousands of servers like it.
Across the catalogue