This record as markdown: /tools/13888285815-windows-mcp/move.md
What Move does on Windows-MCP
AI agents use Move to create or update resources in Windows-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Windows-MCP environment.
Why Move is rated Medium
The Move tool operates on the Windows operating system and likely performs file or window relocation operations. This is a reversible modification (Write category) rather than destructive, as moved items can be moved back. Severity is medium because incorrect moves could displace important files or UI elements, but effects are not permanent or irreversible.
From the tool's definition Tool named 'Move' on Windows-MCP server alongside file system manipulation tools (FileSystem, MultiEdit). Move typically relocates files or windows within the OS, modifying state reversibly.
Attacks that exploit this kind of access
The rule that runs Move 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 Move, this is the rule to start with:
Move 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 Windows-MCP, apply this rule, and every Move call is checked against it from then on.
Questions about Move
Move is a write tool on the Windows MCP server. It is categorised as a Write tool in the Windows-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Windows MCP server in PolicyLayer and add a rule for Move: 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.
Move 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 Move 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 Move. 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.
Move 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.
This server
Across the catalogue