get_battery_status
Get battery status (for laptops): charge percentage, time remaining, power source.
This record as markdown: /tools/19miha99-system-monitor-mcp/get-battery-status.md
What get_battery_status does on Desktop Commander MCP Server
AI agents call get_battery_status to retrieve information from Desktop Commander MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_battery_status is rated Low
This is a pure information retrieval operation that queries the system's battery state without creating, modifying, deleting, or executing any actions. The data returned is read-only telemetry about device power status. Even though the server has broad desktop control capabilities, this specific tool is narrowly scoped to passive monitoring, making it a Read category with low severity.
From the tool's definition Tool retrieves battery status information (charge percentage, time remaining, power source) with no modification of system state or side effects.
Attacks that exploit this kind of access
The rule that runs get_battery_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Desktop Commander MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_battery_status, this is the rule to start with:
get_battery_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Desktop Commander MCP Server, apply this rule, and every get_battery_status call is checked against it from then on.
Questions about get_battery_status
Get battery status (for laptops): charge percentage, time remaining, power source. It is categorised as a Read tool in the Desktop Commander MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Desktop Commander MCP Server MCP server in PolicyLayer and add a rule for get_battery_status: 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 Desktop Commander MCP Server. Nothing to install.
get_battery_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_battery_status 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 get_battery_status. 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.
get_battery_status is provided by the Desktop Commander MCP Server MCP server (19miha99/system-monitor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander MCP Server, and thousands of servers like it.
This server
Across the catalogue