Critical Risk →

draw_remove_one

Remove a specific drawing by entity ID

How to control draw_remove_one ↓

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.

Critical Risk

This tool irreversibly removes/deletes a specific drawing object from the TradingView chart. Deletion of chart drawings is a destructive action as it cannot be easily undone, especially in an automated workflow context.

From the tool's definition Remove a specific drawing by entity ID

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

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 draw_remove_one:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "draw_remove_one"
  ]
}

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

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

Free to start. No card required.

Go deeper

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

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.