AI agents invoke browser_screen_drag to trigger actions in Playwright MCP. 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.
Dragging the mouse in a browser can execute UI actions such as moving files, reordering elements, drawing, interacting with sliders or map controls, and more. The effect depends entirely on the target web application, making this an Execute-category action. Misuse could trigger unintended application-level operations at scale, warranting high severity.
From the tool's definition "Drag left mouse button" — triggers a browser UI interaction (mouse drag) that can manipulate web page elements, move items, trigger drag-and-drop events, or interact with arbitrary web application controls
Documented attack patterns abuse exactly the kind of access browser_screen_drag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_screen_drag:
{
"version": "1",
"default": "deny",
"tools": {
"browser_screen_drag": {
"limits": [
{
"counter": "browser_screen_drag_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_screen_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.
Free to start. No card required.
Drag left mouse button. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_screen_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 Playwright MCP. Nothing to install.
browser_screen_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_screen_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_screen_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_screen_drag is provided by the Playwright MCP server (korwabs/playwright-record-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Playwright MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.