Low Risk

get_device_users

Get list of user profiles on the device (Android multi-user).

How to control get_device_users ↓

What get_device_users does on Android Forensics ADB MCP Server

AI agents call get_device_users to retrieve information from Android Forensics ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_device_users needs a policy

This tool retrieves and enumerates data (user profiles) from an Android device without modifying, deleting, or executing arbitrary code. While deployed in a forensic context where it accesses sensitive device information, the operation itself is a passive data retrieval with no side effects.

From the tool's definition Tool name and description indicate retrieval of user profile information: 'Get list of user profiles on the device'.

Documented attack patterns abuse exactly the kind of access get_device_users gives an agent:

How to control get_device_users

PolicyLayer is an MCP gateway — it sits between your AI agents and Android Forensics ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_device_users:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_device_users": {}
  }
}

get_device_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Android Forensics ADB MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_device_users

What does the get_device_users tool do? +

Get list of user profiles on the device (Android multi-user). It is categorised as a Read tool in the Android Forensics ADB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_device_users? +

Register the Android Forensics ADB MCP Server MCP server in PolicyLayer and add a rule for get_device_users: 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 Android Forensics ADB MCP Server. Nothing to install.

What risk level is get_device_users? +

get_device_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_device_users? +

Yes. Add a rate_limit block to the get_device_users 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.

How do I block get_device_users completely? +

Set action: deny in the PolicyLayer policy for get_device_users. 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.

What MCP server provides get_device_users? +

get_device_users is provided by the Android Forensics ADB MCP Server MCP server (0x-professor/droidforensics-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Android Forensics ADB MCP Server tool call.

Start from Android Forensics ADB MCP Server, 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.

58 Android Forensics ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.