sensor_battery

Set battery level, charging status, and plugged state on Android. Changes persist until reset:true is used or device reboots. iOS: not supported.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What sensor_battery does on Claude Mobile

AI agents call sensor_battery to permanently remove resources in Claude Mobile, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why sensor_battery is rated Critical

An AI agent that decides to call sensor_battery doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Claude Mobile is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sensor_battery 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_battery, this is the rule to start with:

sensor_battery Hidden

sensor_battery is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sensor_battery"
  ]
}

RESTRICT 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_battery call is checked against it from then on.

FAQ

Questions about sensor_battery

What does the sensor_battery tool do? +

Set battery level, charging status, and plugged state on Android. Changes persist until reset:true is used or device reboots. iOS: not supported. It is categorised as a Destructive tool in the Claude Mobile MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sensor_battery? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for sensor_battery: 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_battery? +

sensor_battery is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sensor_battery? +

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

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

sensor_battery 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 → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →