Drag from one coordinate to another
AI agents invoke mouseDrag to trigger actions in PlayMCP Browser Automation 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.
mouseDrag performs a browser automation action (click-and-drag) that can manipulate UI elements, reorder items, move objects, or trigger drag-and-drop events in a running browser session. This is an Execute-category tool because it drives external browser behavior whose effects depend entirely on the target coordinates and application state.
From the tool's definition "Drag from one coordinate to another" — triggers a browser interaction (mouse drag action) that causes external UI state changes depending on arguments
Documented attack patterns abuse exactly the kind of access mouseDrag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PlayMCP Browser Automation Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mouseDrag:
{
"version": "1",
"default": "deny",
"tools": {
"mouseDrag": {
"limits": [
{
"counter": "mousedrag_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mouseDrag 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.
Free to start. No card required.
Drag from one coordinate to another. It is categorised as a Execute tool in the PlayMCP Browser Automation Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PlayMCP Browser Automation Server MCP server in PolicyLayer and add a rule for mouseDrag: 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 PlayMCP Browser Automation Server. Nothing to install.
mouseDrag 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 mouseDrag 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 mouseDrag. 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.
mouseDrag is provided by the PlayMCP Browser Automation Server MCP server (jomon003/playmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PlayMCP Browser Automation Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 PlayMCP Browser Automation Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.