Scroll the chart or page up/down/left/right
AI agents invoke ui_scroll to trigger actions in TradingView MCP Bridge. 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.
This tool performs a browser/UI action (scrolling) through the Chrome DevTools Protocol. It doesn't read data, write/modify persistent data, or delete anything — it executes a UI interaction. The blast radius is low since scrolling is a benign navigation action with no persistent side effects.
From the tool's definition 'Scroll the chart or page up/down/left/right' — triggers a UI interaction/browser action on the TradingView Desktop interface via Chrome DevTools Protocol
Attacks that exploit this kind of access
Scroll the chart or page up/down/left/right. It is categorised as a Execute tool in the TradingView MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for ui_scroll: 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_scroll 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_scroll 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_scroll. 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_scroll is provided by the TradingView MCP Bridge MCP server (thinhbv/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 →