get_device
Gets device details for a given enterprise and device ID. Requires the resource name in the format: enterprises/{enterpriseId}/devices/{deviceId}.
This record as markdown: /tools/com-googleapis-androidmanagement-mcp/get-device.md
What get_device does on Android Management API
AI agents call get_device 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 |
|---|---|---|---|
name | string | — | The name of the device in the form `enterprises/{enterpriseId}/devices/{deviceId}`. |
Parameters from the server's own tool schema.
Why get_device is rated Low
This is a read operation that retrieves device information without side effects. However, severity is elevated to 'high' because: (1) Android Management API context indicates enterprise/mobile device management with sensitive operational control; (2) device details in enterprise MDM contexts typically include security configuration, enrollment status, compliance posture, and potentially user association data; (3)…
From the tool's definition Tool description states 'Gets device details' with specified resource name format (enterprises/{enterpriseId}/devices/{deviceId}). Returns queried data with no modification.
Attacks that exploit this kind of access
The rule that runs get_device 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 get_device, this is the rule to start with:
get_device 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 get_device call is checked against it from then on.
Questions about get_device
Gets device details for a given enterprise and device ID. Requires the resource name in the format: enterprises/{enterpriseId}/devices/{deviceId}. It is categorised as a Read tool in the Android Management API MCP Server, which means it retrieves data without modifying state.
get_device accepts 1 parameter: name. 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 get_device: 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.
get_device 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 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. 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 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