ui_find_element

Find UI elements by text, aria-label, or CSS selector and return their positions

SERVERTradingView MCP Bridge SOURCEbyeung888/tradingview-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What ui_find_element does on TradingView MCP Bridge

AI agents call ui_find_element to retrieve information from TradingView MCP Bridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ui_find_element is rated Low

This is a query/search operation that locates and returns metadata about UI elements. It has no side effects, does not execute code or commands, does not modify data, and does not perform destructive or financial operations. It is foundational tooling for UI automation but on its own only reads and reports element positions.

From the tool's definition Tool description states it 'Find[s] UI elements by text, aria-label, or CSS selector and return[s] their positions' — purely retrieves information about UI element locations without modifying state or triggering actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ui_find_element 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_find_element, this is the rule to start with:

ui_find_element Allowed

ui_find_element is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_find_element": {}
  }
}

ALLOW ONLY 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_find_element call is checked against it from then on.

FAQ

Questions about ui_find_element

What does the ui_find_element tool do? +

Find UI elements by text, aria-label, or CSS selector and return their positions. It is categorised as a Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ui_find_element? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for ui_find_element: 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_find_element? +

ui_find_element is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ui_find_element? +

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

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

ui_find_element 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →