Change screen resolution - useful for testing different screen sizes
AI agents invoke change_screen_size to trigger actions in Enhanced ADB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Changing screen resolution modifies device display settings at a system level. While potentially reversible, it affects the entire device state and all running applications. It executes a system-level ADB command that alters device configuration, placing it in the Execute category. Misuse could disrupt device usability and ongoing workflows, warranting high severity.
From the tool's definition Change screen resolution - useful for testing different screen sizes
Attacks that exploit this kind of access
Change screen resolution - useful for testing different screen sizes. It is categorised as a Execute tool in the Enhanced ADB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for change_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 Enhanced ADB MCP Server. Nothing to install.
change_screen_size is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the change_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 change_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.
change_screen_size 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 →