This record as markdown: /tools/byeung888-tradingview-mcp/alert-list.md
What alert_list does on TradingView MCP Bridge
AI agents call alert_list 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 alert_list is rated Low
This tool retrieves and displays alert configuration data from TradingView without side effects. It queries the state of the application but does not create, modify, delete, or trigger any alerts. This is a pure read operation with minimal security risk—the worst outcome is information disclosure about existing alerts.
From the tool's definition Tool name 'alert_list' with description 'List active alerts' indicates querying/retrieving existing alert data without modification or execution of alerts themselves.
Attacks that exploit this kind of access
The rule that runs alert_list 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 alert_list, this is the rule to start with:
alert_list 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 alert_list call is checked against it from then on.
Questions about alert_list
List active alerts. 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 alert_list: 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.
alert_list 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 alert_list 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 alert_list. 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.
alert_list 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