drag_mouse
AI agents invoke drag_mouse to trigger actions in Computer Control Mcp Lands. 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.
Drag mouse is a UI automation action that can interact with arbitrary UI elements — moving files, resizing windows, drawing, triggering drag-and-drop operations. This constitutes execution of external operations whose effects depend on arguments. The description is empty, lowering confidence slightly, but the server context and sibling tools strongly imply this is a mouse drag automation action.
From the tool's definition Tool name 'drag_mouse' on a server providing 'mouse and keyboard automation' and 'computer control capabilities'; sibling tools include click_screen, move_mouse, press_key, type_text.
Attacks that exploit this kind of access
drag_mouse. It is categorised as a Execute tool in the Computer Control Mcp Lands MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer Control Mcp Lands MCP server in PolicyLayer and add a rule for drag_mouse: 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 Computer Control Mcp Lands. Nothing to install.
drag_mouse 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_mouse 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_mouse. 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_mouse is provided by the Computer Control Mcp Lands MCP server (songcaiya/windows-mcp-lands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →