Perform drag and drop operations between two elements on a web page. Supports reordering items in sortable lists, moving cards in kanban boards, dragging files to upload zones, rearranging table rows, and other interactive drag and drop scenarios. Automatically handles mouse events (mousedown, mo...
AI agents invoke browser_drag to trigger actions in MCP Macaco Playwright. 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.
This tool executes browser interactions (drag-and-drop UI actions) that trigger external operations on a web page. Effects depend on the target page and arguments — could reorder data, upload files, or modify application state. It's an Execute-category action as it drives real browser behavior with variable outcomes.
From the tool's definition Perform drag and drop operations between two elements on a web page... Automatically handles mouse events (mousedown, mousemove, mouseup) required for complete drag operations
Attacks that exploit this kind of access
Perform drag and drop operations between two elements on a web page. Supports reordering items in sortable lists, moving cards in kanban boards, dragging files to upload zones, rearranging table rows, and other interactive drag and drop scenarios. Automatically handles mouse events (mousedown, mousemove, mouseup) required for complete drag operations. It is categorised as a Execute tool in the MCP Macaco Playwright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Macaco Playwright MCP server in PolicyLayer and add a rule for browser_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 MCP Macaco Playwright. Nothing to install.
browser_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 browser_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 browser_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.
browser_drag is provided by the MCP Macaco Playwright MCP server (macacoai/mcp-playwright). 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 →