Low Risk

xpath_screenshot

xpath_screenshot

How to control xpath_screenshot ↓

What xpath_screenshot does on uiautomator2 MCP Server

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

Low Risk

Why xpath_screenshot needs a policy

Screenshots capture visual/UI data without modifying device state or triggering side effects. The empty description lowers confidence slightly, but naming and sibling tools (activity_wait_appear, app_list, etc.) establish this as an Android UI inspection tool. No code execution, data modification, or destructive operations occur. Retrieving screen state is a read operation with minimal blast radius if misused.

From the tool's definition Tool name 'xpath_screenshot' and context indicates it captures screen state for UI inspection via xpath queries, similar to 'screenshot' operations in UI automation frameworks.

Documented attack patterns abuse exactly the kind of access xpath_screenshot gives an agent:

How to control xpath_screenshot

PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for xpath_screenshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "xpath_screenshot": {}
  }
}

xpath_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register uiautomator2 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about xpath_screenshot

What does the xpath_screenshot tool do? +

xpath_screenshot. It is categorised as a Read tool in the uiautomator2 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on xpath_screenshot? +

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

What risk level is xpath_screenshot? +

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

Can I rate-limit xpath_screenshot? +

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

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

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

Enforce policy on every uiautomator2 MCP Server tool call.

Start from uiautomator2 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.