This record as markdown: /tools/async23-chrome-devtools-mcp/drag.md
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 drag is rated High
Dragging an element onto another triggers UI interactions in a browser (e.g., drag-and-drop events), which can cause side effects like reordering items, moving files, or triggering application logic. This is a browser action/execution, not a simple read or write to a data store. Severity is medium because misuse could manipulate web application state, but is generally reversible and scoped to the browser session.
From the tool's definition "Drag an element onto another element" — triggers a browser interaction/action that manipulates the state of a web page
Attacks that exploit this kind of access
The rule that runs drag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every drag call is checked against it from then on.
Questions about drag
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.
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.
drag is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
drag is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue