New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

alert_delete

Delete all alerts or open context menu for deletion

SERVERTradingView MCP Server SOURCEdebarpan2000/tradingview-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about alert_delete

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 Server 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 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.

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 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TradingView MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.