Drag an element (like cards in a kanban board) onto a target element. Useful for sortable UIs.
AI agents invoke browser_drag to trigger actions in YetiBrowser 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.
This tool performs a browser interaction (drag-and-drop) that triggers external operations in the web page UI, such as reordering items, moving cards between columns, or repositioning elements. The effect depends on the target application's behavior and can cause state changes in web applications, making it an Execute-category action.
From the tool's definition Drag an element (like cards in a kanban board) onto a target element. Useful for sortable UIs.
Documented attack patterns abuse exactly the kind of access browser_drag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YetiBrowser MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_drag:
{
"version": "1",
"default": "deny",
"tools": {
"browser_drag": {
"limits": [
{
"counter": "browser_drag_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_drag 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 an element (like cards in a kanban board) onto a target element. Useful for sortable UIs. It is categorised as a Execute tool in the YetiBrowser MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the YetiBrowser MCP server in PolicyLayer and add a rule for browser_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 YetiBrowser MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_drag is provided by the YetiBrowser MCP server (yetidevworks/yetibrowser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from YetiBrowser MCP, 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.
17 YetiBrowser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.