This record as markdown: /tools/debarpan2000-tradingview-mcp/alert-list.md
What alert_list does on TradingView MCP Server
AI agents call alert_list to retrieve information from TradingView MCP Server 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
The tool retrieves and displays information about existing alerts. This is a read-only operation that poses minimal risk. Even if an AI agent misuses it, the worst outcome is information disclosure about the user's alerts, which is low severity. No data is modified, deleted, or financial transactions are triggered.
From the tool's definition Tool name is 'alert_list' with description 'List active alerts' — this is a retrieval operation with no side effects. It queries existing alert data without modification, creation, or deletion.
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 Server, 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 Server, 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 Server MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Server 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 Server. 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 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.
This server
Across the catalogue