browser_drop

A execute tool on the Playwright MCP server.

SERVERPlaywright SOURCEhanato238/playwright-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hanato238-playwright-mcp/browser-drop.md

WHAT IT DOES

What browser_drop does on Playwright

AI agents invoke browser_drop to trigger actions in 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.

RISK

Why browser_drop is rated High

Based on the sibling tool 'browser_drag', this tool likely completes a drag-and-drop interaction in the browser, which constitutes executing a browser action. The empty description lowers confidence, but the naming pattern and context of a browser automation server suggest it triggers an external browser operation.

From the tool's definition Tool name 'browser_drop' on a browser automation MCP server; description is empty.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_drop safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_drop, this is the rule to start with:

browser_drop Rate-limited

browser_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": {
    "browser_drop": {
      "limits": [
        {
          "counter": "browser_drop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Playwright, apply this rule, and every browser_drop call is checked against it from then on.

FAQ

Questions about browser_drop

What does the browser_drop tool do? +

browser_drop is a execute tool on the Playwright MCP server. It is categorised as a Execute tool in the Playwright 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_drop? +

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

What risk level is browser_drop? +

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

Can I rate-limit browser_drop? +

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

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

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

KEEP EXPLORING

More on Playwright, and thousands of servers like it.

This server

All 66 Playwright tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →