Get Android device information and capabilities
AI agents call get_android_device_info to retrieve information from MCP Prompts 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 returns device information (properties, capabilities, status) without creating, modifying, executing, or deleting anything. It is a pure read operation with minimal security risk—device info is typically non-sensitive or already accessible to the app runtime. The blast radius of an AI agent misusing this is negligible.
From the tool's definition Tool name 'get_android_device_info' and description 'Get Android device information and capabilities' indicate data retrieval with no modification or execution of operations.
Documented attack patterns abuse exactly the kind of access get_android_device_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Prompts Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_android_device_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_android_device_info": {}
}
}get_android_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 Android device information and capabilities. It is categorised as a Read tool in the MCP Prompts Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Prompts Server MCP server in PolicyLayer and add a rule for get_android_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 Prompts Server. Nothing to install.
get_android_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_android_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_android_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_android_device_info is provided by the MCP Prompts Server MCP server (sparesparrow/mcp-prompts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 MCP Prompts Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 MCP Prompts Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.