sensor
Sensor & Environment Simulation. location: set GPS coordinates. battery: set battery level/status. notifications: read notification shade. thermal: set thermal status.
This record as markdown: /tools/alexgladkov-claude-in-mobile/sensor.md
What sensor does on Claude Mobile
AI agents invoke sensor 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.
Why sensor is rated High
This tool both reads data (notification shade) and actively manipulates device environment/state (GPS spoofing, battery simulation, thermal state). Environment simulation via GPS spoofing is particularly dangerous as it can deceive location-dependent apps or services. The most severe applicable category is Execute, as it triggers external device operations with real effects on device behavior.
From the tool's definition 'set GPS coordinates', 'set battery level/status', 'set thermal status', 'read notification shade' — the tool simulates/overrides hardware sensors and reads device notifications
Attacks that exploit this kind of access
The rule that runs sensor 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, this is the rule to start with:
sensor 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every sensor call is checked against it from then on.
Questions about sensor
Sensor & Environment Simulation. location: set GPS coordinates. battery: set battery level/status. notifications: read notification shade. thermal: set thermal status. 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.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for sensor: 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.
sensor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sensor 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. 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 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.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue