ui_evaluate
Execute JavaScript code in the TradingView page context for advanced automation
This record as markdown: /tools/debarpan2000-tradingview-mcp/ui-evaluate.md
What ui_evaluate does on TradingView MCP Server
AI agents invoke ui_evaluate to trigger actions in TradingView MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ui_evaluate is rated High
This tool allows arbitrary code execution in the context of a financial trading platform. JavaScript execution in a browser context with access to TradingView's DOM and APIs could allow an agent to modify orders, execute trades, access account credentials, extract sensitive data, or perform unauthorized actions.
From the tool's definition Execute JavaScript code in the TradingView page context for advanced automation. The tool explicitly permits execution of arbitrary JavaScript within a live trading application.
Attacks that exploit this kind of access
The rule that runs ui_evaluate 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_evaluate, this is the rule to start with:
ui_evaluate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_evaluate call is checked against it from then on.
Questions about ui_evaluate
Execute JavaScript code in the TradingView page context for advanced automation. It is categorised as a Execute tool in the TradingView MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for ui_evaluate: 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_evaluate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ui_evaluate 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_evaluate. 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_evaluate 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.
Across the catalogue