Returns the screen density of the connected Android device. No parameters are required.
AI agents call wm_density to retrieve information from Ultimate Android MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and returns the screen density property of an Android device. It has no parameters, makes no modifications to device state, executes no code or commands, and causes no side effects. It is analogous to a simple getter or information retrieval operation, making it the lowest severity category.
From the tool's definition Tool name 'wm_density' and description 'Returns the screen density of the connected Android device' indicates a query operation that retrieves device information without modifying or executing any operations.
Documented attack patterns abuse exactly the kind of access wm_density gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ultimate Android MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for wm_density:
{
"version": "1",
"default": "deny",
"tools": {
"wm_density": {}
}
} wm_density 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.
Returns the screen density of the connected Android device. No parameters are required. It is categorised as a Read tool in the Ultimate Android MCP MCP Server, which means it retrieves data without modifying state.
Register the Ultimate Android MCP server in PolicyLayer and add a rule for wm_density: 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 Ultimate Android MCP. Nothing to install.
wm_density 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 wm_density 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 wm_density. 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.
wm_density is provided by the Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ultimate Android MCP, 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.
35 Ultimate Android MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.