sensor_set · Android Emulator MCP: Risk & Policy

WHAT IT DOES

What sensor_set does on Android Emulator

AI agents use sensor_set to create or update resources in Android Emulator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android Emulator environment.

WHY IT NEEDS A POLICY

Why sensor_set needs a policy

Based on the server description mentioning control over virtual sensors (accelerometer, gyroscope) and the sibling tools 'sensor_get' and 'sensor_status', 'sensor_set' almost certainly sets/modifies sensor values on the Android emulator. This is a Write operation as it modifies emulator state reversibly.

From the tool's definition Tool name 'sensor_set' on a server that 'provides control over virtual sensors like the accelerometer and gyroscope'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sensor_set Rate-limited

sensor_set stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sensor_set": {
      "limits": [
        {
          "counter": "sensor_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Android Emulator, so you can run agents against it safely.

FAQ

Questions about sensor_set

What does the sensor_set tool do? +

sensor_set. It is categorised as a Write tool in the Android Emulator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sensor_set? +

Register the Android Emulator MCP server in PolicyLayer and add a rule for sensor_set: 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.

What risk level is sensor_set? +

sensor_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sensor_set? +

Yes. Add a rate_limit block to the sensor_set 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 sensor_set completely? +

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

sensor_set 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.