Get and display monitor power management settings
AI agents call monitor_power_settings to retrieve information from Mcp Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays monitor power settings without creating, modifying, deleting, or executing operations. It is a read-only query of system configuration state. The low severity reflects minimal blast radius—incorrect usage would only return misleading information rather than cause harm.
From the tool's definition Tool name 'monitor_power_settings' and description 'Get and display monitor power management settings' indicate retrieval of existing configuration data with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access monitor_power_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for monitor_power_settings:
{
"version": "1",
"default": "deny",
"tools": {
"monitor_power_settings": {}
}
}monitor_power_settings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get and display monitor power management settings. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for monitor_power_settings: 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 Windows. Nothing to install.
monitor_power_settings 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 monitor_power_settings 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 monitor_power_settings. 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.
monitor_power_settings is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.