Draw a Risk/Reward LONG or SHORT position tool natively at the current bar, with entry, stop-loss and take-profit set to exact prices IN ONE CALL. This is the ONLY correct way to visualize a proposed trade — do NOT use horizontal_line or rectangle for trade setups. Direction is auto-detected from...
AI agents use draw_position 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.
This tool creates and modifies chart annotations/drawings (position tools) reversibly. While it doesn't execute trades or move money, it does create persistent chart objects that represent trading setups. The action is reversible (drawings can be deleted), making it Write rather than Execute or Destructive.
From the tool's definition Tool creates a position visualization drawing on a chart with entry, stop-loss, and take-profit parameters at the current bar.
Attacks that exploit this kind of access
Draw a Risk/Reward LONG or SHORT position tool natively at the current bar, with entry, stop-loss and take-profit set to exact prices IN ONE CALL. This is the ONLY correct way to visualize a proposed trade — do NOT use horizontal_line or rectangle for trade setups. Direction is auto-detected from prices (long: sl < entry < tp, short: sl > entry > tp). Symbol tick size is read automatically from symbolInfo.pricescale/minmov so this works for crypto (BTC tick 0.01), futures (MNQ/MES tick 0.25), forex, and stocks. REJECTS setups with R:R < 2 by default (pass min_rr to override, not recommended). 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.
Register the TradingView MCP server in PolicyLayer and add a rule for draw_position: 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_position is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the draw_position 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_position. 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_position 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 →