watchlist_get
Get all symbols from the current TradingView watchlist with last price, change, and change%
This record as markdown: /tools/byeung888-tradingview-mcp/watchlist-get.md
What watchlist_get does on TradingView MCP Bridge
AI agents call watchlist_get to retrieve information from TradingView MCP Bridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why watchlist_get is rated Low
This tool only queries and returns data (watchlist symbols with price information) with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The severity is low because the data retrieved is non-sensitive market data already visible in the user's own TradingView interface, and there are no destructive, financial, or execution risks.
From the tool's definition Tool name is 'watchlist_get' and description states 'Get all symbols from the current TradingView watchlist with last price, change, and change%' - purely a retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs watchlist_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For watchlist_get, this is the rule to start with:
watchlist_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every watchlist_get call is checked against it from then on.
Questions about watchlist_get
Get all symbols from the current TradingView watchlist with last price, change, and change%. 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 watchlist_get: 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.
watchlist_get 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 watchlist_get 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 watchlist_get. 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.
watchlist_get is provided by the TradingView MCP Bridge MCP server (byeung888/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 Bridge, and thousands of servers like it.
This server
Across the catalogue