AI agents call inspect_ui to retrieve information from ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
inspect_ui most likely retrieves or queries UI state/hierarchy from an Android device without modifying it, aligning with the 'Read' category. However, confidence is reduced from 0.9 to 0.85 due to empty description; if the tool unexpectedly executes code or modifies UI state, this classification would be incorrect.
From the tool's definition Tool named 'inspect_ui' with empty description; inferred from context as UI inspection/analysis capability. Server description mentions 'UI analysis' as a capability.
Documented attack patterns abuse exactly the kind of access inspect_ui gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for inspect_ui:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_ui": {}
}
}inspect_ui is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
inspect_ui. It is categorised as a Read tool in the ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for inspect_ui: 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 ADB MCP Server. Nothing to install.
inspect_ui is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the inspect_ui 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.
Set action: deny in the PolicyLayer policy for inspect_ui. 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.
inspect_ui is provided by the ADB MCP Server MCP server (srmorete/adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 ADB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 ADB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.