This record as markdown: /tools/mukul975-mcp-windows-automation/wifi-profiles-list.md
What wifi_profiles_list does on Mcp Windows
AI agents call wifi_profiles_list to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wifi_profiles_list is rated Low
The tool queries and returns existing WiFi profile data without creating, modifying, deleting, or executing any operations. It is a passive read-only action with minimal blast radius even if misused by an AI agent, as it only exposes already-configured WiFi profiles on the system.
From the tool's definition Tool name contains 'list' and description states 'List saved WiFi profiles' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs wifi_profiles_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wifi_profiles_list, this is the rule to start with:
wifi_profiles_list 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 Mcp Windows, apply this rule, and every wifi_profiles_list call is checked against it from then on.
Questions about wifi_profiles_list
List saved WiFi profiles. 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 wifi_profiles_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 Windows. Nothing to install.
wifi_profiles_list 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 wifi_profiles_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 wifi_profiles_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.
wifi_profiles_list 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.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue