drags an element and drops it onto another element
AI agents invoke drag_and_drop to trigger actions in MCP Selenium 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 action that executes an interactive operation in a live browser session. Its effects depend on the application under control and can range from reordering items to triggering uploads or workflow state changes, making it Execute-category with medium severity.
From the tool's definition 'drags an element and drops it onto another element' — triggers browser UI interaction that manipulates DOM state and can invoke arbitrary application-side effects depending on the target
Attacks that exploit this kind of access
drags an element and drops it onto another element. It is categorised as a Execute tool in the MCP Selenium Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Selenium 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 MCP Selenium 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 MCP Selenium Server MCP server (sapangupta63/mcp-selenium-extended). 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 →