adb_a11y_touch_targets

List all interactive elements with their touch target dimensions in dp. Highlights elements below the 48dp minimum. Useful for quickly identifying cramped UI layouts.

SERVERDeepadb SOURCEdeepadb

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/io-github-fullread-deepadb/adb-a11y-touch-targets.md

WHAT IT DOES

What adb_a11y_touch_targets does on Deepadb

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

RISK

Why adb_a11y_touch_targets is rated Low

This tool retrieves and displays accessibility metadata (touch target dimensions) from the Android device UI tree. It performs only read-only inspection of UI properties to identify potential accessibility issues. There are no side effects, no data modification, no code execution, and no destructive operations. The blast radius of misuse is minimal—an agent could only gather information about UI layout dimensions.

From the tool's definition Tool description states it 'List[s] all interactive elements' and 'Highlights elements below the 48dp minimum' — purely a query and analysis operation with no data modification or command execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_a11y_touch_targets safely

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

adb_a11y_touch_targets Allowed

adb_a11y_touch_targets 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": {
    "adb_a11y_touch_targets": {}
  }
}

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

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

FAQ

Questions about adb_a11y_touch_targets

What does the adb_a11y_touch_targets tool do? +

List all interactive elements with their touch target dimensions in dp. Highlights elements below the 48dp minimum. Useful for quickly identifying cramped UI layouts. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_a11y_touch_targets? +

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

What risk level is adb_a11y_touch_targets? +

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

Can I rate-limit adb_a11y_touch_targets? +

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

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

adb_a11y_touch_targets is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools →

Across the catalogue

The MCP Attack Database →

Guides

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