android_uiautomator_scroll_in_element

WHAT IT DOES

What android_uiautomator_scroll_in_element does on Android MCP Server

AI agents invoke android_uiautomator_scroll_in_element to trigger actions in Android MCP Server. 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 android_uiautomator_scroll_in_element needs a policy

This tool executes a UI automation action (scrolling within an element) on a remote Android device. It is not purely a read operation since it triggers an input event/gesture, but it doesn't write data or cause irreversible destruction. It falls under Execute as it performs an external operation on a device whose effects depend on the arguments (which element to scroll, how far, etc.).

From the tool's definition 'Scroll within a specific UI element' — triggers a physical UI interaction (scroll gesture) on an Android device via ADB automation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_uiautomator_scroll_in_element Rate-limited

android_uiautomator_scroll_in_element 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": {
    "android_uiautomator_scroll_in_element": {
      "limits": [
        {
          "counter": "android_uiautomator_scroll_in_element_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 Android MCP Server, so you can run agents against it safely.

FAQ

Questions about android_uiautomator_scroll_in_element

What does the android_uiautomator_scroll_in_element tool do? +

Scroll within a specific UI element. It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on android_uiautomator_scroll_in_element? +

Register the Android MCP Server MCP server in PolicyLayer and add a rule for android_uiautomator_scroll_in_element: 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 Server. Nothing to install.

What risk level is android_uiautomator_scroll_in_element? +

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

Can I rate-limit android_uiautomator_scroll_in_element? +

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

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

android_uiautomator_scroll_in_element is provided by the Android MCP Server MCP server (jduartedj/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.