input.drag
Press-move-release mouse drag in native capture coordinates. Use for drawing, sliders, selection boxes, and drag-and-drop. Side effect: mouse_down → moves → mouse_up on the remote desktop. Prefer input.send_actions if the drag is one step in a longer predictable sequence.
This record as markdown: /tools/com-glasswarp-mcp-server/input.drag.md
What input.drag does on Glasswarp
AI agents invoke input.drag to trigger actions in Glasswarp. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
to_x | integer | Yes | Native end X |
to_y | integer | Yes | Native end Y |
from_x | integer | Yes | Native start X |
from_y | integer | Yes | Native start Y |
session_id | string | Yes | Active session id |
duration_ms | integer | — | Approx drag duration in ms; more steps when larger (default ~200) |
Parameters from the server's own tool schema.
Why input.drag is rated High
Triggers real mouse drag actions on a remote Windows desktop with direct side effects.
From the tool's definition mouse_down → moves → mouse_up on the remote desktop
Attacks that exploit this kind of access
The rule that runs input.drag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Glasswarp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For input.drag, this is the rule to start with:
input.drag 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 Glasswarp, apply this rule, and every input.drag call is checked against it from then on.
Questions about input.drag
Press-move-release mouse drag in native capture coordinates. Use for drawing, sliders, selection boxes, and drag-and-drop. Side effect: mouse_down → moves → mouse_up on the remote desktop. Prefer input.send_actions if the drag is one step in a longer predictable sequence. It is categorised as a Execute tool in the Glasswarp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
input.drag accepts 6 parameters: to_x, to_y, from_x, from_y, session_id, duration_ms. Required: to_x, to_y, from_x, from_y, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Glasswarp MCP server in PolicyLayer and add a rule for input.drag: 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 Glasswarp. Nothing to install.
input.drag 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 input.drag 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 input.drag. 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.
input.drag is provided by the Glasswarp MCP server (https://mcp.glasswarp.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Glasswarp, and thousands of servers like it.
Across the catalogue