browser_drag
Perform drag and drop between two elements
This record as markdown: /tools/a11y-agent-skills/browser-drag.md
What browser_drag does on A11y Agent Skills
AI agents invoke browser_drag to trigger actions in A11y Agent Skills. 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.
Why browser_drag is rated High
Drag and drop is a browser action that causes external side effects depending on arguments (e.g., reordering items, moving files, triggering drop events). It does not merely read data, and its effects vary widely based on context. It fits the Execute category as it triggers an external UI operation whose outcome depends on which elements are targeted.
From the tool's definition "Perform drag and drop between two elements" — triggers a browser interaction that manipulates UI state
Attacks that exploit this kind of access
The rule that runs browser_drag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A11y Agent Skills, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_drag, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect A11y Agent Skills, apply this rule, and every browser_drag call is checked against it from then on.
Questions about browser_drag
Perform drag and drop between two elements. It is categorised as a Execute tool in the A11y Agent Skills MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the A11y Agent Skills 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 A11y Agent Skills. 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 A11y Agent Skills MCP server (smukh/a11y-agent-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A11y Agent Skills, and thousands of servers like it.
Across the catalogue