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 Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/search operation that returns information (element positions) without creating, modifying, deleting, or executing any actions. It is a read-only utility for UI introspection, similar to DOM query methods. While it could theoretically be chained with other tools (e.g., ui_click) to perform side effects, the tool itself is strictly informational.
From the tool's definition Tool description states 'Find UI elements by text, aria-label, or CSS selector and return their positions' — it retrieves positional data about UI elements with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access ui_find_element gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for ui_find_element:
{
"version": "1",
"default": "deny",
"tools": {
"ui_find_element": {}
}
}ui_find_element is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
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 Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.