ui_drag
AI agents invoke ui_drag to trigger actions in UI Bridge 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.
The name 'ui_drag' strongly implies a drag interaction on a UI element — a physical UI action that triggers external operations in the target application. This is an Execute-category action (browser/UI automation). The description is empty, which lowers confidence, but the server context (UI interaction, control mode) and sibling tools like 'sdk_ai_execute' confirm this is an action-triggering server.
From the tool's definition Tool name 'ui_drag' on a UI Bridge MCP server that 'enables AI to inspect and interact with UI elements' and supports 'control mode' and 'SDK mode for external applications'
Attacks that exploit this kind of access
ui_drag. It is categorised as a Execute tool in the UI Bridge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UI Bridge MCP server in PolicyLayer and add a rule for ui_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 UI Bridge MCP. Nothing to install.
ui_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 ui_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 ui_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.
ui_drag is provided by the UI Bridge MCP server (qontinui/ui-bridge-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 →