capture_ui_dump

THE RISK

Low Risk

Why capture_ui_dump needs a policy

This tool reads and retrieves the current UI structure/hierarchy from the Android device. It performs a read-only operation with no side effects, similar to a screenshot but for UI element data. No data is modified, created, or deleted.

From the tool's definition Capture UI hierarchy dump from the device

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

POLICY

How to control capture_ui_dump

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

policy.json

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

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

Create a free account and register Android Debug Bridge MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Android Debug Bridge MCP tools

Execute input_keyevent Send key events (BACK, HOME, ENTER, DELETE) Execute input_scroll Perform scroll action Execute input_tap Tap at specific coordinates Execute input_text Input text into the current field Execute open_app Open an app using its package name and activity Write create_test_folder Create a test folder with the specified name Read capture_screenshot Capture a screenshot and save it to the test folder Read list_apps List installed apps matching a name pattern

All 9 Android Debug Bridge MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about capture_ui_dump

What does the capture_ui_dump tool do? +

Capture UI hierarchy dump from the device. It is categorised as a Read tool in the Android Debug Bridge MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_ui_dump? +

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

What risk level is capture_ui_dump? +

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

Can I rate-limit capture_ui_dump? +

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

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

capture_ui_dump is provided by the Android Debug Bridge MCP server (tiagodanin/android-debug-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Android Debug Bridge MCP tool call.

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

CHECK YOUR STACK →