Get comprehensive device information including serial number, screen resolution, Android version, SDK level, battery status, WiFi IP address, manufacturer, model, and current screen state
AI agents call get_device_info to retrieve information from MCP Android Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries device metadata without side effects. It does not create, modify, delete, or execute any operations—it only reads and reports existing device state. The blast radius of misuse is minimal: an attacker could learn device characteristics but cannot directly harm the device or user data through this tool alone.
From the tool's definition Tool description explicitly states it 'Get[s] comprehensive device information' including serial number, screen resolution, Android version, SDK level, battery status, WiFi IP address, manufacturer, model, and current screen state.
Documented attack patterns abuse exactly the kind of access get_device_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Android Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for get_device_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_info": {}
}
}get_device_info 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.
Get comprehensive device information including serial number, screen resolution, Android version, SDK level, battery status, WiFi IP address, manufacturer, model, and current screen state. It is categorised as a Read tool in the MCP Android Agent MCP Server, which means it retrieves data without modifying state.
Register the MCP Android Agent MCP server in PolicyLayer and add a rule for get_device_info: 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 MCP Android Agent. Nothing to install.
get_device_info 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_device_info 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_device_info. 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_device_info is provided by the MCP Android Agent MCP server (nim444/mcp-android-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 MCP Android Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
28 MCP Android Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.