drag_to
Drag the mouse to screen coordinates.
This record as markdown: /tools/mcp-control-plane/drag-to.md
What drag_to does on Mcp Control Plane
AI agents invoke drag_to to trigger actions in Mcp Control Plane. 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_to is rated High
This tool performs a UI automation action (mouse drag) that can interact with any on-screen element, potentially moving files, manipulating UI controls, or triggering arbitrary application behavior depending on the coordinates used. It is an execution of an external operation whose effects depend on arguments (the target coordinates), making it Execute.
From the tool's definition "Drag the mouse to screen coordinates" — triggers a physical mouse drag action on the user's screen
Attacks that exploit this kind of access
The rule that runs drag_to safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drag_to, this is the rule to start with:
drag_to 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 Control Plane, apply this rule, and every drag_to call is checked against it from then on.
Questions about drag_to
Drag the mouse to screen coordinates. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for drag_to: 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 Control Plane. Nothing to install.
drag_to 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_to 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_to. 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_to is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue