drag · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What drag does on Chrome Devtools

AI agents invoke drag to trigger actions in Chrome Devtools. 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 needs a policy

Dragging elements in a live browser is an Execute-level action: it triggers real browser UI interactions whose effects depend on what is dragged and where. It could move files, reorder data, or trigger drop-zone handlers with side effects. It is not purely Read, and its reversibility depends on what the drop target does, making Execute the most accurate category.

From the tool's definition "Drag an element onto another element" — triggers a browser interaction (drag-and-drop) that causes UI state changes depending on the target element

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

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 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. 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 (nimbus21/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.