drag_and_drop · MCP Playwright Server MCP: Risk & Policy

WHAT IT DOES

What drag_and_drop does on MCP Playwright Server

AI agents invoke drag_and_drop to trigger actions in MCP Playwright Server. 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 IT NEEDS A POLICY

Why drag_and_drop needs a policy

Drag-and-drop is a browser action that executes UI interactions in an external browser context. While it doesn't inherently delete or write data, it triggers operations whose effects entirely depend on what the target application does (e.g., reordering, moving files, changing configurations). This falls under Execute as it performs external browser operations with variable side effects.

From the tool's definition 'Drag an element and drop it on another element' — triggers browser interaction that manipulates UI elements, potentially causing state changes in a web application

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drag_and_drop Rate-limited

drag_and_drop 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drag_and_drop": {
      "limits": [
        {
          "counter": "drag_and_drop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Playwright Server, so you can run agents against it safely.

FAQ

Questions about drag_and_drop

What does the drag_and_drop tool do? +

Drag an element and drop it on another element. Supports automatic retries for flaky elements. It is categorised as a Execute tool in the MCP Playwright Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on drag_and_drop? +

Register the MCP Playwright Server MCP server in PolicyLayer and add a rule for drag_and_drop: 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 Playwright Server. Nothing to install.

What risk level is drag_and_drop? +

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

Can I rate-limit drag_and_drop? +

Yes. Add a rate_limit block to the drag_and_drop 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 drag_and_drop completely? +

Set action: deny in the PolicyLayer policy for drag_and_drop. 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 drag_and_drop? +

drag_and_drop is provided by the MCP Playwright Server MCP server (j0hanz/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.