New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ui_find_element

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

SERVERTradingView MCP Server SOURCEdebarpan2000/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/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.

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 Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ui_find_element? +

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TradingView MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.