ui_double_click · UI Bridge MCP: Risk & Policy

WHAT IT DOES

What ui_double_click does on UI Bridge MCP

AI agents invoke ui_double_click 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.

WHY IT NEEDS A POLICY

Why ui_double_click needs a policy

This tool performs a UI interaction (double-clicking an element), which triggers external operations in a UI environment. Double-clicking can open files, launch applications, confirm dialogs, or trigger other significant actions depending on the target element. It falls under Execute as it performs actions with effects dependent on the arguments (which element is clicked).

From the tool's definition Double-click an element in the runner

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ui_double_click Rate-limited

ui_double_click 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_double_click": {
      "limits": [
        {
          "counter": "ui_double_click_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UI Bridge MCP, so you can run agents against it safely.

FAQ

Questions about ui_double_click

What does the ui_double_click tool do? +

Double-click an element in the runner. 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.

How do I enforce a policy on ui_double_click? +

Register the UI Bridge MCP server in PolicyLayer and add a rule for ui_double_click: 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.

What risk level is ui_double_click? +

ui_double_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ui_double_click? +

Yes. Add a rate_limit block to the ui_double_click 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.

How do I block ui_double_click completely? +

Set action: deny in the PolicyLayer policy for ui_double_click. 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.

What MCP server provides ui_double_click? +

ui_double_click 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.