Delete all alerts or open context menu for deletion
AI agents call alert_delete to permanently remove resources in TradingView MCP Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of alerts without recovery. Deletion is a classic destructive operation. While alerts themselves are not financial transactions, their loss is permanent and could disrupt trading workflows or analysis. The 'all alerts' capability increases blast radius significantly.
From the tool's definition Tool name 'alert_delete' and description 'Delete all alerts' explicitly indicate irreversible deletion of user data (alerts). The phrase 'Delete all alerts' confirms the destructive nature.
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 Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TradingView MCP Bridge 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 Bridge. 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 Bridge MCP server (thinhbv/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 →