browser_drag_drop · Browser MCP: Risk & Policy

WHAT IT DOES

What browser_drag_drop does on BrowserMCP

AI agents use browser_drag_drop to create or update resources in BrowserMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BrowserMCP environment.

WHY IT NEEDS A POLICY

Why browser_drag_drop needs a policy

An AI agent can call browser_drag_drop faster than any human can review — one bad instruction and it creates or modifies resources in BrowserMCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_drag_drop Rate-limited

browser_drag_drop stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_drag_drop": {
      "limits": [
        {
          "counter": "browser_drag_drop_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about browser_drag_drop

What does the browser_drag_drop tool do? +

Drag an element and drop it onto another element. It is categorised as a Write tool in the BrowserMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_drag_drop? +

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

What risk level is browser_drag_drop? +

browser_drag_drop is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_drag_drop? +

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

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

browser_drag_drop is provided by the Browser MCP server (smotree/browsermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.