power_plan_list
Every power scheme known to powercfg, the active one, and the balanced/high/saver alias map.
This record as markdown: /tools/mcp-hands/power-plan-list.md
What power_plan_list does on Mcp Hands
AI agents use power_plan_list to create or update resources in Mcp Hands, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Hands environment.
Why power_plan_list is rated Medium
An AI agent can call power_plan_list faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Hands by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs power_plan_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Hands, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For power_plan_list, this is the rule to start with:
power_plan_list stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Hands, apply this rule, and every power_plan_list call is checked against it from then on.
Questions about power_plan_list
Every power scheme known to powercfg, the active one, and the balanced/high/saver alias map. It is categorised as a Write tool in the Mcp Hands MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Hands MCP server in PolicyLayer and add a rule for power_plan_list: 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 Mcp Hands. Nothing to install.
power_plan_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the power_plan_list 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 power_plan_list. 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.
power_plan_list is provided by the Mcp Hands MCP server (huocai250/mcp-hands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Hands, and thousands of servers like it.
This server
Across the catalogue