drag_and_drop
Drag from start coordinates to end coordinates
This record as markdown: /tools/mukul975-mcp-windows-automation/drag-and-drop.md
What drag_and_drop does on Mcp Windows
AI agents invoke drag_and_drop to trigger actions in Mcp Windows. 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 drag_and_drop is rated High
This tool performs a UI interaction (drag-and-drop) that triggers external operations on the Windows system. The effect depends on the arguments (source and destination coordinates), making it Execute. Misuse could rearrange files, move UI elements, or trigger unintended actions depending on what is under the coordinates.
From the tool's definition Drag from start coordinates to end coordinates
Attacks that exploit this kind of access
The rule that runs drag_and_drop 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 drag_and_drop, this is the rule to start with:
drag_and_drop 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 Mcp Windows, apply this rule, and every drag_and_drop call is checked against it from then on.
Questions about drag_and_drop
Drag from start coordinates to end coordinates. It is categorised as a Execute tool in the Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for drag_and_drop: 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.
drag_and_drop 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 drag_and_drop 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 drag_and_drop. 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.
drag_and_drop 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.
Across the catalogue