drag

Drag an element onto another element

SERVERChrome DevTools MCP SOURCEanirbandz/chrome_mcp_devtool

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/anirbandz-chrome-mcp-devtool/drag.md

WHAT IT DOES

What drag does on Chrome DevTools MCP

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

RISK

Why drag is rated High

Dragging an element onto another is a browser action that executes a user-interaction sequence via Chrome DevTools Protocol. The effect depends on the target application's response to the drag-and-drop event, making it Execute. It is not purely destructive or financial, but misuse could trigger unintended application state changes.

From the tool's definition "Drag an element onto another element" — triggers a browser interaction (drag-and-drop) that manipulates the live Chrome browser UI and may cause side effects depending on the target application (e.g., reordering, moving files, triggering UI events).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drag safely

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

drag Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drag": {
      "limits": [
        {
          "counter": "drag_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 Chrome DevTools MCP, apply this rule, and every drag call is checked against it from then on.

FAQ

Questions about drag

What does the drag tool do? +

Drag an element onto another element. It is categorised as a Execute tool in the Chrome DevTools MCP 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? +

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

What risk level is drag? +

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

Can I rate-limit drag? +

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

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

drag is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome DevTools, and thousands of servers like it.

This server

All 26 Chrome DevTools tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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