Delete all alerts or open context menu for deletion
AI agents call alert_delete to permanently remove resources in Tradingview — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes alerts without recovery option. While the blast radius is somewhat contained (alerts are not financial transactions themselves), deletion of trading alerts could lead to missed trade signals or missed risk management, making it a high-severity destructive action. The phrase 'Delete all alerts' indicates the tool can irreversibly destroy multiple alert configurations at once.
From the tool's definition Tool name is 'alert_delete' and description states 'Delete all alerts' — irreversible deletion of alert configurations.
Attacks that exploit this kind of access
Delete all alerts or open context menu for deletion. It is categorised as a Destructive tool in the Tradingview MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tradingview 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. 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 (lionfaion/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 →