alert_delete

THE RISK

Critical Risk

This tool permanently removes alerts without the ability to restore them. While the impact is scoped to alerts rather than financial data or trades, the irreversible nature of deletion and the potential for cascade effects (e.g., missing critical market alerts) if misused by an AI agent classifies this as Destructive rather than Write.

From the tool's definition 'Delete all alerts' explicitly indicates irreversible removal of alert objects. This is a destructive operation that cannot be undone—once alerts are deleted, they cannot be recovered.

Documented attack patterns abuse exactly the kind of access alert_delete gives an agent:

HOW TO CONTROL ALERT_DELETE

PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for alert_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "alert_delete"
  ]
}

alert_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register TradingView MCP Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More TradingView MCP Bridge tools

Destructive draw_clear Remove all drawings from the chart Destructive draw_remove_one Remove a specific drawing by entity ID Execute batch_run Run an action across multiple symbols and/or timeframes Execute pine_compile Compile / add the current Pine Script to the chart Execute pine_smart_compile Intelligent compile: detects button, compiles, checks errors, reports study changes Execute replay_start Start bar replay mode, optionally at a specific date Execute replay_stop Stop replay and return to realtime Execute replay_trade Execute a trade action in replay mode (buy, sell, or close position)

All 78 TradingView MCP Bridge tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in TradingView MCP Bridge → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the alert_delete tool do? +

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.

How do I enforce a policy on alert_delete? +

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.

What risk level is alert_delete? +

alert_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit alert_delete? +

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.

How do I block alert_delete completely? +

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.

What MCP server provides alert_delete? +

alert_delete is provided by the TradingView MCP Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TradingView MCP Bridge tool call.

Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN TRADINGVIEW MCP BRIDGE →

Free to start. No card required.

78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT ALERT_DELETE ON TRADINGVIEW MCP BRIDGE DOES

// THE RISK

// HOW TO CONTROL ALERT_DELETE

// EXPLORE