ui_find_element
Find UI elements by text, aria-label, or CSS selector and return their positions
This record as markdown: /tools/debarpan2000-tradingview-mcp/ui-find-element.md
What ui_find_element does on TradingView MCP Server
AI agents call ui_find_element to retrieve information from TradingView MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ui_find_element is rated Low
This tool only locates and returns information about UI element positions. It performs no side effects, creates no data modifications, executes no scripts, and triggers no external operations. It is purely informational, analogous to a DOM query. While it could theoretically be chained with other tools to enable harmful actions, the tool itself is read-only and presents minimal risk if misused in isolation.
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' — a query operation that retrieves element metadata without modifying state or triggering actions.
Attacks that exploit this kind of access
The rule that runs ui_find_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every ui_find_element call is checked against it from then on.
Questions about ui_find_element
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 Server MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Server 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 Server. Nothing to install.
ui_find_element is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
ui_find_element is provided by the TradingView MCP Server MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TradingView MCP Server, and thousands of servers like it.
This server
Across the catalogue