Returns the device overlay configuration properties of the connected Android device. No parameters are required.
AI agents call list_features to retrieve information from Ultimate Android MCP 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 existing device configuration properties without creating, modifying, deleting, or executing any operations. It is purely informational, consistent with other Read category tools like get_battery_level and get_properties on the same server. The lack of parameters and passive nature of returning properties confirms it poses minimal security risk.
From the tool's definition Tool name 'list_features' and description 'Returns the device overlay configuration properties' indicate a retrieval operation with no side effects or modifications.
Documented attack patterns abuse exactly the kind of access list_features gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ultimate Android MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_features:
{
"version": "1",
"default": "deny",
"tools": {
"list_features": {}
}
} list_features 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.
Returns the device overlay configuration properties of the connected Android device. No parameters are required. It is categorised as a Read tool in the Ultimate Android MCP MCP Server, which means it retrieves data without modifying state.
Register the Ultimate Android MCP server in PolicyLayer and add a rule for list_features: 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 Ultimate Android MCP. Nothing to install.
list_features 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 list_features 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 list_features. 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.
list_features is provided by the Ultimate Android MCP server (oddlyspaced/ultimate-android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ultimate Android MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Ultimate Android MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.