draw_move · TradingView MCP: Risk & Policy

WHAT IT DOES

What draw_move does on TradingView MCP

AI agents use draw_move to create or update resources in TradingView MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP environment.

WHY IT NEEDS A POLICY

Why draw_move needs a policy

This tool modifies existing drawings on a TradingView chart by moving them—a reversible write operation. It does not execute trading logic, delete drawings, or move financial instruments. The severity is medium because unintended drawing modifications could obscure chart analysis or mislead a user reviewing charting annotations, but the effect is limited in scope and easily undone.

From the tool's definition Tool description states it 'Translate[s] a drawing by a relative delta' and 'offsets every point equally', indicating modification of existing chart drawing objects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

draw_move Rate-limited

draw_move stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "draw_move": {
      "limits": [
        {
          "counter": "draw_move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TradingView MCP, so you can run agents against it safely.

FAQ

Questions about draw_move

What does the draw_move tool do? +

Translate a drawing by a relative delta in time and/or price. Works for any multi-point shape — offsets every point equally. It is categorised as a Write tool in the TradingView MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on draw_move? +

Register the TradingView MCP server in PolicyLayer and add a rule for draw_move: 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.

What risk level is draw_move? +

draw_move is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit draw_move? +

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

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

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