computer_drag
Drag from x1,y1 to x2,y2 (screenshot coordinates). Requires approval (risk 3).
This record as markdown: /tools/yuga-hashimoto-localant/computer-drag.md
What computer_drag does on LocalAnt
AI agents invoke computer_drag to trigger actions in LocalAnt. 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 computer_drag is rated High
This tool performs a physical UI interaction (drag action) on the user's PC via browser/desktop automation. It triggers an external operation whose effect depends on arguments (coordinates), placing it in the Execute category. The 'risk 3' approval requirement and the broad potential for misuse (dragging files, UI elements, triggering actions) give it high severity.
From the tool's definition Drag from x1,y1 to x2,y2 (screenshot coordinates). Requires approval (risk 3).
Attacks that exploit this kind of access
The rule that runs computer_drag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For computer_drag, this is the rule to start with:
computer_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 LocalAnt, apply this rule, and every computer_drag call is checked against it from then on.
Questions about computer_drag
Drag from x1,y1 to x2,y2 (screenshot coordinates). Requires approval (risk 3). It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LocalAnt MCP server in PolicyLayer and add a rule for computer_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 LocalAnt. Nothing to install.
computer_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 computer_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 computer_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.
computer_drag is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
Across the catalogue