Drag from one point to another
AI agents invoke drag to trigger actions in BrowserPilot MCP. 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.
Dragging is a browser automation action that executes a physical UI interaction. Its effects are context-dependent: it could reorder elements, move files, interact with web app widgets, or trigger other operations. This qualifies as Execute since it performs an external browser operation with variable outcomes based on arguments.
From the tool's definition "Drag from one point to another" — triggers a browser interaction (drag action) that performs a UI operation whose effects depend entirely on what element is dragged and where it is dropped.
Attacks that exploit this kind of access
Drag from one point to another. It is categorised as a Execute tool in the BrowserPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BrowserPilot 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 BrowserPilot MCP. 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 BrowserPilot MCP server (sept-7-qi/browserpilot-mcp). 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 →