draw_remove_one

Remove a specific drawing by entity ID

SERVERTradingView MCP Bridge SOURCEbyeung888/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/byeung888-tradingview-mcp/draw-remove-one.md

What draw_remove_one does on TradingView MCP Bridge

AI agents call draw_remove_one 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.

Why draw_remove_one is rated Critical

This tool irreversibly deletes user-created drawings/annotations from TradingView charts. While not data corruption at the database level, the action is non-reversible and represents permanent loss of user work product. High severity reflects that an agent could destroy significant analytical work (trend lines, patterns, notes) across multiple charts without undo capability.

From the tool's definition 'Remove a specific drawing by entity ID' indicates permanent deletion of user-created chart drawings without recovery option.

Questions about draw_remove_one

What does the draw_remove_one tool do? +

Remove a specific drawing by entity ID. 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 draw_remove_one? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for draw_remove_one: 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 draw_remove_one? +

draw_remove_one 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 draw_remove_one? +

Yes. Add a rate_limit block to the draw_remove_one 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 draw_remove_one completely? +

Set action: deny in the PolicyLayer policy for draw_remove_one. 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 draw_remove_one? +

draw_remove_one is provided by the TradingView MCP Bridge MCP server (byeung888/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 Bridge, 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 Bridge'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.