ui_hover · Tradingview MCP: Risk & Policy

WHAT IT DOES

What ui_hover does on Tradingview

AI agents invoke ui_hover to trigger actions in Tradingview. 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_hover needs a policy

This tool performs a UI interaction (hover) on the locally running TradingView Desktop app via CDP. It executes an external operation in the browser context. While hover itself typically has minimal side effects, it can trigger UI state changes (dropdowns, tooltips, menus) that may set up subsequent actions. It's classified as Execute since it triggers external operations in the application.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

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 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 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. 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 server (lionfaion/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.