draw_remove_one
Remove a specific drawing by entity ID
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.
Attacks that exploit this kind of access
The rule that runs draw_remove_one safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For draw_remove_one, this is the rule to start with:
draw_remove_one is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every draw_remove_one call is checked against it from then on.
Questions about draw_remove_one
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.
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.
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.
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.
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.
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.
Across the catalogue