This record as markdown: /tools/yuga-hashimoto-localant/adb-screen-size.md
What adb_screen_size does on LocalAnt
AI agents call adb_screen_size to retrieve information from LocalAnt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_screen_size is rated Low
This tool queries static device information (screen dimensions) with no side effects, no code execution, and no data modification or deletion. It is a straightforward read operation on device metadata. Low severity because the information retrieved is non-sensitive device capability data that poses minimal risk if disclosed or queried.
From the tool's definition Tool name 'adb_screen_size' and description 'Get the device screen size' indicate a query operation that retrieves display dimensions from an Android device via ADB without modification.
Attacks that exploit this kind of access
The rule that runs adb_screen_size safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_screen_size, this is the rule to start with:
adb_screen_size is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_screen_size call is checked against it from then on.
Questions about adb_screen_size
Get the device screen size. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.
Register the LocalAnt MCP server in PolicyLayer and add a rule for adb_screen_size: 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 LocalAnt. Nothing to install.
adb_screen_size 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 adb_screen_size 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 adb_screen_size. 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.
adb_screen_size is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
This server
Across the catalogue