sensor_thermal
Override Android thermal status (API 29+ / Android 10+). Simulates device overheating scenarios. Use reset:true to restore real thermal state. iOS: not supported.
This record as markdown: /tools/alexgladkov-claude-in-mobile/sensor-thermal.md
What sensor_thermal does on Claude Mobile
AI agents invoke sensor_thermal 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_thermal is rated High
This tool executes a system-level override on the Android device, artificially changing its thermal state. It triggers external hardware/OS behavior and can simulate overheating, which could affect device performance, throttle CPU/GPU, or trigger protective shutdowns. It is reversible via reset:true, ruling out Destructive. It falls under Execute as it runs a system command that changes device operating state.
From the tool's definition Override Android thermal status... Simulates device overheating scenarios. Use reset:true to restore real thermal state.
Attacks that exploit this kind of access
The rule that runs sensor_thermal 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_thermal, this is the rule to start with:
sensor_thermal 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_thermal call is checked against it from then on.
Questions about sensor_thermal
Override Android thermal status (API 29+ / Android 10+). Simulates device overheating scenarios. Use reset:true to restore real thermal state. iOS: not supported. 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_thermal: 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_thermal 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_thermal 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_thermal. 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_thermal 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