find_element

Find element by text

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/find-element.md

WHAT IT DOES

What find_element does on Claude Mobile

AI agents call find_element to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_element is rated Low

The tool searches for and returns information about UI elements matching specified text criteria. It does not create, modify, delete, or execute any actions—it only scans and reports on existing UI state. This is consistent with Read category semantics (retrieves or queries data; no side effects).

From the tool's definition Tool name 'find_element' and description 'Find element by text' indicate a query/search operation that locates UI elements without modifying state. This is a read-only operation that retrieves information about the current screen state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_element safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_element, this is the rule to start with:

find_element Allowed

find_element is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_element": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every find_element call is checked against it from then on.

FAQ

Questions about find_element

What does the find_element tool do? +

Find element by text. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_element? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for find_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 Claude Mobile. Nothing to install.

What risk level is find_element? +

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

Can I rate-limit find_element? +

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

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

find_element is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →