list_devices
Lists devices for a given enterprise. Requires the enterprise ID in the parent field (e.g., enterprises/{enterpriseId}).
This record as markdown: /tools/com-googleapis-androidmanagement-mcp/list-devices.md
What list_devices does on Android Management API
AI agents call list_devices to retrieve information from Android Management API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
parent | string | — | The name of the enterprise in the form `enterprises/{enterpriseId}`. |
pageSize | integer | — | The requested page size. If unspecified, at most 10 devices will be returned. The maximum value is 100; values above 100 will be coerced to 100. The limits can |
pageToken | string | — | A token identifying a page of results returned by the server. |
Parameters from the server's own tool schema.
Why list_devices is rated Low
This tool queries and retrieves a list of devices managed by an enterprise. It performs no side effects, creation, modification, or deletion of data. However, severity is elevated to 'medium' because device lists in an MDM context may contain sensitive information (device identities, ownership details, configurations) that could be misused if exposed to an unauthorized agent, potentially enabling reconnaissance or…
From the tool's definition Tool name is 'list_devices' and description states it 'Lists devices for a given enterprise' — a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs list_devices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Android Management API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_devices, this is the rule to start with:
list_devices is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Android Management API, apply this rule, and every list_devices call is checked against it from then on.
Questions about list_devices
Lists devices for a given enterprise. Requires the enterprise ID in the parent field (e.g., enterprises/{enterpriseId}). It is categorised as a Read tool in the Android Management API MCP Server, which means it retrieves data without modifying state.
list_devices accepts 3 parameters: parent, pageSize, pageToken. The full parameter table on this page comes from the server's own tool schema.
Register the Android Management API MCP server in PolicyLayer and add a rule for list_devices: 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 Management API. Nothing to install.
list_devices 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_devices 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_devices. 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_devices is provided by the Android Management API MCP server (https://androidmanagement.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Android Management API, and thousands of servers like it.
This server
Across the catalogue