get_clickable_elements

Get all clickable/interactive elements on screen with their coordinates.

Server Enhanced ADB MCP Server rahulkr/r_adb_mcp_server
Category Read
Risk class Low
Parameters 00 required

What get_clickable_elements does on Enhanced ADB MCP Server

AI agents call get_clickable_elements to retrieve information from Enhanced ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_clickable_elements needs a policy

This tool queries the current UI state and returns information about interactive elements. It performs no modifications, deletions, or external operations. While it enables reconnaissance for subsequent actions, the tool itself is purely informational (Read category). Severity is low because knowing element positions poses minimal risk even if misused—it cannot alter system state or device behavior.

From the tool's definition Tool description states 'Get all clickable/interactive elements on screen with their coordinates' — a retrieval operation with no side effects.

Questions about get_clickable_elements

What does the get_clickable_elements tool do? +

Get all clickable/interactive elements on screen with their coordinates. It is categorised as a Read tool in the Enhanced ADB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_clickable_elements? +

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

What risk level is get_clickable_elements? +

get_clickable_elements is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_clickable_elements? +

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

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

get_clickable_elements is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

get_clickable_elements is one line of Enhanced ADB MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.