browser_mouse_drag_xy
Drag left mouse button to a given position
This record as markdown: /tools/cowork-bench/browser-mouse-drag-xy.md
What browser_mouse_drag_xy does on Cowork Bench
AI agents invoke browser_mouse_drag_xy to trigger actions in Cowork Bench. 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 browser_mouse_drag_xy is rated High
This tool performs a browser-level mouse drag action, which is an external operation that can interact with any UI element on screen. Misuse could manipulate web applications, move files, trigger drag-and-drop operations with unintended consequences, or interact with sensitive UI components. It falls under Execute as it triggers external operations whose effects depend on arguments (target coordinates).
From the tool's definition 'Drag left mouse button to a given position' — triggers a browser mouse drag action, an external UI interaction
Attacks that exploit this kind of access
The rule that runs browser_mouse_drag_xy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_mouse_drag_xy, this is the rule to start with:
browser_mouse_drag_xy 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 Cowork Bench, apply this rule, and every browser_mouse_drag_xy call is checked against it from then on.
Questions about browser_mouse_drag_xy
Drag left mouse button to a given position. It is categorised as a Execute tool in the Cowork Bench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for browser_mouse_drag_xy: 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 Cowork Bench. Nothing to install.
browser_mouse_drag_xy 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 browser_mouse_drag_xy 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 browser_mouse_drag_xy. 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.
browser_mouse_drag_xy is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
Across the catalogue