Remove all drawings from the chart
AI agents call draw_clear to permanently remove resources in TradingView MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes all user-created drawings from a trading chart without restoration capability. While the blast radius is confined to chart annotations (not financial losses directly), it represents destruction of work product that cannot be undone. Classified as Destructive rather than Write because the operation is one-way deletion (remove all) rather than reversible modification.
From the tool's definition Tool name 'draw_clear' with description 'Remove all drawings from the chart' indicates irreversible deletion of chart annotations/drawings. The verb 'Remove all' and lack of undo mechanism in context of automated chart manipulation suggests permanent erasure.
Attacks that exploit this kind of access
Remove all drawings from the chart. It is categorised as a Destructive tool in the TradingView MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TradingView MCP server in PolicyLayer and add a rule for draw_clear: 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. Nothing to install.
draw_clear 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_clear 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_clear. 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_clear is provided by the TradingView MCP server (ulianbass/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 →