ui_mouse_click
Click at specific x,y coordinates on the TradingView window
This record as markdown: /tools/debarpan2000-tradingview-mcp/ui-mouse-click.md
What ui_mouse_click does on TradingView MCP Server
AI agents invoke ui_mouse_click 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_mouse_click is rated High
Clicking at arbitrary coordinates in a trading application can trigger any UI action, including placing orders, modifying trades, or activating financial operations. This is an Execute-level action because it drives external application behavior whose effects are entirely dependent on what is at those coordinates.
From the tool's definition 'Click at specific x,y coordinates on the TradingView window' — triggers UI interaction via mouse click at arbitrary coordinates
Attacks that exploit this kind of access
The rule that runs ui_mouse_click 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_mouse_click, this is the rule to start with:
ui_mouse_click 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_mouse_click call is checked against it from then on.
Questions about ui_mouse_click
Click at specific x,y coordinates on the TradingView window. 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_mouse_click: 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_mouse_click 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_mouse_click 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_mouse_click. 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_mouse_click 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