set_battery_state · AVD MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_battery_state does on AVD MCP Server

AI agents invoke set_battery_state to trigger actions in AVD MCP Server. 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 IT NEEDS A POLICY

Why set_battery_state needs a policy

This tool executes an Android system command (dumpsys battery) to modify the emulator's battery state. It is not a simple read operation, nor does it destroy data or move money. It runs a system-level command with side effects on the virtual device's simulated hardware state, placing it in the Execute category.

From the tool's definition 'Ajusta estado de bateria (nível/carga) via dumpsys battery' — triggers external Android system command (dumpsys battery) to change device battery state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_battery_state Rate-limited

set_battery_state 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": {
    "set_battery_state": {
      "limits": [
        {
          "counter": "set_battery_state_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about set_battery_state

What does the set_battery_state tool do? +

Ajusta estado de bateria (nível/carga) via dumpsys battery. It is categorised as a Execute tool in the AVD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_battery_state? +

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

What risk level is set_battery_state? +

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

Can I rate-limit set_battery_state? +

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

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

set_battery_state is provided by the AVD MCP Server MCP server (jramalho/avd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.