MultiSelect
Selects multiple items such as files, folders, or checkboxes if press_ctrl=True, or performs multiple clicks if False. Pass locs (list of coordinates) or labels (list of UI element labels/ids).
This record as markdown: /tools/13888285815-windows-mcp/multiselect.md
What MultiSelect does on Windows-MCP
AI agents invoke MultiSelect to trigger actions in Windows-MCP. 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 MultiSelect is rated High
This tool simulates user input by performing multiple clicks or multi-selections on UI elements. It triggers external OS-level interactions (UI automation, simulated input) whose effects depend on what is being selected and subsequently acted upon. While selection alone is not destructive, it is an Execute-class action because it drives UI automation and can precede destructive or sensitive operations.
From the tool's definition Selects multiple items such as files, folders, or checkboxes if press_ctrl=True, or performs multiple clicks if False. Pass locs (list of coordinates) or labels (list of UI element labels/ids).
Attacks that exploit this kind of access
The rule that runs MultiSelect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Windows-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For MultiSelect, this is the rule to start with:
MultiSelect 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Windows-MCP, apply this rule, and every MultiSelect call is checked against it from then on.
Questions about MultiSelect
Selects multiple items such as files, folders, or checkboxes if press_ctrl=True, or performs multiple clicks if False. Pass locs (list of coordinates) or labels (list of UI element labels/ids). It is categorised as a Execute tool in the Windows-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Windows MCP server in PolicyLayer and add a rule for MultiSelect: 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 Windows-MCP. Nothing to install.
MultiSelect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the MultiSelect 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 MultiSelect. 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.
MultiSelect is provided by the Windows MCP server (13888285815/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Windows, and thousands of servers like it.
Across the catalogue