Get detailed screen specifications - useful for responsive design
AI agents call get_screen_specs to retrieve information from Enhanced ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves screen specification data from an Android device via ADB. It performs a read-only operation with no side effects, no code execution, and no data modification. The information retrieved (screen dimensions, density, etc.) is benign metadata useful for responsive design testing.
From the tool's definition Tool name is 'get_screen_specs' and description states 'Get detailed screen specifications' - a retrieval operation with no modification or execution of commands.
Attacks that exploit this kind of access
Get detailed screen specifications - useful for responsive design. It is categorised as a Read tool in the Enhanced ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for get_screen_specs: 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 Enhanced ADB MCP Server. Nothing to install.
get_screen_specs 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 get_screen_specs 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 get_screen_specs. 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.
get_screen_specs is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →