ドラッグアンドドロップ操作を実行します
AI agents invoke drag_and_drop to trigger actions in Playwright MCP Server. 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.
Drag-and-drop is a browser interaction/action that triggers external operations on web pages. Its effects depend on the target element and page context (e.g., reordering items, moving files, triggering UI events). This classifies as Execute — it runs a browser action whose outcome depends on arguments.
From the tool's definition 「ドラッグアンドドロップ操作を実行します」 — translates to 'Executes drag-and-drop operations'; part of a Playwright browser automation server with sibling tools like mouse_click, navigate
Attacks that exploit this kind of access
ドラッグアンドドロップ操作を実行します. It is categorised as a Execute tool in the Playwright MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for drag_and_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 Playwright MCP Server. Nothing to install.
drag_and_drop 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_and_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.
Set action: deny in the PolicyLayer policy for drag_and_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.
drag_and_drop is provided by the Playwright MCP Server MCP server (kotelberg/playwright-mcp-server). 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 →