List all available sensors and their status on a running emulator.
AI agents call sensor_status to retrieve information from Android Emulator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists sensor metadata and status from an emulator. It performs no side effects, creates no changes, executes no commands, and poses no destructive or financial risk. This is a straightforward read operation.
From the tool's definition Tool name 'sensor_status' and description 'List all available sensors and their status on a running emulator' indicate a query operation that retrieves sensor information without modifying or executing actions.
Attacks that exploit this kind of access
List all available sensors and their status on a running emulator. It is categorised as a Read tool in the Android Emulator MCP Server, which means it retrieves data without modifying state.
Register the Android Emulator MCP server in PolicyLayer and add a rule for sensor_status: 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 Emulator. Nothing to install.
sensor_status 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 sensor_status 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 sensor_status. 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.
sensor_status is provided by the Android Emulator MCP server (janjetze/android-emulator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →