browser_screen_drag | PolicyLayer

WHAT IT DOES

What browser_screen_drag does on Playwright MCP with Electron Support

AI agents invoke browser_screen_drag to trigger actions in Playwright MCP with Electron Support. 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.

THE RISK

High Risk

Why browser_screen_drag needs a policy

This tool executes a UI interaction (mouse drag) within a browser or Electron app. Its effects depend entirely on the context and target element, potentially triggering application-level actions such as reordering, moving files, or manipulating UI state.

From the tool's definition 'Drag left mouse button' — performs a physical mouse drag interaction in a browser or Electron desktop application

Documented attack patterns abuse exactly the kind of access browser_screen_drag gives an agent:

POLICY

How to control browser_screen_drag

PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP with Electron Support, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_screen_drag:

policy.json

{
  "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.

Create a free account and register Playwright MCP with Electron Support — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Playwright MCP with Electron Support tools

Destructive browser_close Close the page Destructive browser_tab_close Close a tab Execute browser_navigate Navigate to a URL Execute browser_navigate_back Go back to the previous page Execute browser_navigate_forward Go forward to the next page Execute browser_tab_new Open a new tab Execute browser_wait_for Wait for text to appear or disappear or a specified time to pass Execute browser_click Perform click on a web page

All 34 Playwright MCP with Electron Support tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Playwright MCP with Electron Support → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about browser_screen_drag

What does the browser_screen_drag tool do? +

Drag left mouse button. It is categorised as a Execute tool in the Playwright MCP with Electron Support MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_screen_drag? +

Register the Playwright MCP with Electron Support 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 with Electron Support. Nothing to install.

What risk level is browser_screen_drag? +

browser_screen_drag is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_screen_drag? +

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.

How do I block browser_screen_drag completely? +

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.

What MCP server provides browser_screen_drag? +

browser_screen_drag is provided by the Playwright MCP with Electron Support MCP server (robertn702/playwright-mcp-electron). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Playwright MCP with Electron Support tool call.

Start from Playwright MCP with Electron Support, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

34 Playwright MCP with Electron Support tools catalogued and risk-classified — across an index of 43,000+ MCP servers.