Find UI elements by text, aria-label, or CSS selector and return their positions
AI agents call ui_find_element to retrieve information from TradingView MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only locates and returns information about UI element positions. It retrieves data about the TradingView interface state without creating, modifying, executing, or destroying anything. The capability to find elements is a prerequisite for interaction but is itself a read-only operation, making it the least risky category on the spectrum.
From the tool's definition Tool description states 'Find UI elements by text, aria-label, or CSS selector and return their positions' - a pure query/discovery operation with no modification, execution, or side effects.
Attacks that exploit this kind of access
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 MCP Server, which means it retrieves data without modifying state.
Register the TradingView 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. 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 (ulianbass/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →