alert_delete
Delete all alerts or open context menu for deletion
This record as markdown: /tools/debarpan2000-tradingview-mcp/alert-delete.md
What alert_delete does on TradingView MCP Server
AI agents call alert_delete to permanently remove resources in TradingView MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why alert_delete is rated Critical
This tool permanently removes alerts without reversibility. While the scope is limited to alert objects (not financial instruments or funds), deleting all alerts can disrupt trading workflows, cause missed market notifications, and cannot be undone. This warrants Destructive classification over Execute due to the irreversible nature of the operation.
From the tool's definition Tool name 'alert_delete' combined with description 'Delete all alerts or open context menu for deletion' indicates irreversible deletion of alert objects. The phrase 'delete all alerts' suggests bulk destructive capability.
Attacks that exploit this kind of access
The rule that runs alert_delete 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_delete, this is the rule to start with:
alert_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every alert_delete call is checked against it from then on.
Questions about alert_delete
Delete all alerts or open context menu for deletion. It is categorised as a Destructive tool in the TradingView MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for alert_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the alert_delete 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_delete. 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_delete 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