sensor_location

Set GPS location on device. Android emulator: uses

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/sensor-location.md

WHAT IT DOES

What sensor_location does on Claude Mobile

AI agents invoke sensor_location to trigger actions in Claude Mobile. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why sensor_location is rated High

This tool sets the GPS location on a device (Android emulator or iOS Simulator), which is an external operation that changes device sensor state. It doesn't permanently delete data (not Destructive) or move money (not Financial), but it executes a device-level command that alters system state. Misuse could enable location spoofing, affecting location-aware apps or tests, warranting medium severity.

From the tool's definition 'Set GPS location on device' — triggers an external operation that modifies the device's simulated GPS/location state

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sensor_location safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sensor_location, this is the rule to start with:

sensor_location Rate-limited

sensor_location stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_location": {
      "limits": [
        {
          "counter": "sensor_location_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every sensor_location call is checked against it from then on.

FAQ

Questions about sensor_location

What does the sensor_location tool do? +

Set GPS location on device. Android emulator: uses. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sensor_location? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for sensor_location: 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 Claude Mobile. Nothing to install.

What risk level is sensor_location? +

sensor_location is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sensor_location? +

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

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

sensor_location is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →