ui_hover

Hover over a UI element by aria-label, data-name, or text content

SERVERTradingView MCP Bridge SOURCEbyeung888/tradingview-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/byeung888-tradingview-mcp/ui-hover.md

WHAT IT DOES

What ui_hover does on TradingView MCP Bridge

AI agents invoke ui_hover to trigger actions in TradingView MCP Bridge. 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.

RISK

Why ui_hover is rated High

This tool performs a UI action (hover) on the TradingView desktop app through Chrome DevTools Protocol. It is an Execute category action because it triggers an external operation (UI interaction) whose effects depend on the arguments passed.

From the tool's definition 'Hover over a UI element' - triggers an external browser/UI interaction via Chrome DevTools Protocol

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ui_hover safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ui_hover, this is the rule to start with:

ui_hover Rate-limited

ui_hover 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_hover": {
      "limits": [
        {
          "counter": "ui_hover_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every ui_hover call is checked against it from then on.

FAQ

Questions about ui_hover

What does the ui_hover tool do? +

Hover over a UI element by aria-label, data-name, or text content. It is categorised as a Execute tool in the TradingView MCP Bridge 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_hover? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for ui_hover: 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 TradingView MCP Bridge. Nothing to install.

What risk level is ui_hover? +

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

Can I rate-limit ui_hover? +

Yes. Add a rate_limit block to the ui_hover 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_hover completely? +

Set action: deny in the PolicyLayer policy for ui_hover. 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_hover? +

ui_hover is provided by the TradingView MCP Bridge MCP server (byeung888/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Bridge, and thousands of servers like it.

This server

All 78 TradingView MCP Bridge tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →