Drag an element to a target location
AI agents invoke playwright_drag to trigger actions in Playwright MCP Server for Security. 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.
This tool performs a browser interaction (drag-and-drop) that triggers real-time actions on web pages. Depending on the target application, dragging elements can trigger significant operations such as moving files, reorganizing data, or interacting with web UI components in ways that may have downstream effects. It falls under Execute as it performs browser actions whose effects depend on the arguments provided.
From the tool's definition Drag an element to a target location
Attacks that exploit this kind of access
Drag an element to a target location. It is categorised as a Execute tool in the Playwright MCP Server for Security MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP Server for Security MCP server in PolicyLayer and add a rule for playwright_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 Playwright MCP Server for Security. Nothing to install.
playwright_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 playwright_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 playwright_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.
playwright_drag is provided by the Playwright MCP Server for Security MCP server (o0x1024/mcp-playwright-security). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →